Liquid Flow Computer Manual (2510 software)...7.7.1 Introduction 7.16 7.7.2 Worked Examples 7.17...

Liquid Flow Computer Manual (2510 software)

7951 Flow ComputerOperating Manual HB512510 June 2009

7951

Klippon Connector Model

D-Type Connector Model

Introduction:

The 7951 liquid flow computer can be used for single stream applications. As standard, there is support for Pipe Proving and Master Meter Proving on D-type connector models. Software Version:

2510 – Liquid Applications. Models Covered:

7951EAA6***** Models Covered: 7951EAB6*****

Emerson Process Management (EPM) pursues a policy of continuous development and product improvement. The information contained in this document is, therefore, subject to change without notice. To the best of our knowledge, the information contained in this document is accurate. However, EPM cannot be held responsible for any errors, omissions or inaccuracies, or any losses incurred as result of them.

IMPORTANT NOTICE Because we are continuously improving our products, some of the menus which appear on your instrument’s display may not be exactly as illustrated and described in this manual. However, because the menus are simple and intuitive, this should not cause any major problems.

This manual is concurrent with embedded software version 512510, issue 4.30.00 (or higher)

Static precautions Some parts of the instrument (such as circuit boards) may be damaged by static electricity. Therefore, when carrying out any work which involves the risk of static damage to the instrument, the instructions show the following notice:

CAUTION While carrying out this procedure, you must wear an earthed wrist strap at all times to protect the instrument against static shock.

At such times you must wear an earthed wrist-strap to protect the instrument.

Safety information NOTE: This information applies only to those instruments which are mains-powered. Electricity is dangerous and you risk injury or death if you do not disconnect the power supplies before carrying out some of the procedures given in this manual. Whenever there is such a hazard, the instructions show a notice similar to the following:

WARNING Electricity is dangerous and can kill. Disconnect all power supplies before proceeding.

You must heed any such warnings and make sure that, before you go any further: All power leads are un-powered.

All power leads are disconnected from the equipment which you are working on unless the instructions tell you otherwise.

You obey any other common-sense precautions which may apply to your situation.

If you obey these sensible precautions, you can work on the equipment in complete safety.

Battery-backed Memory notice It is essential that the Lithium Cell used for the battery backup is installed at all times (other than during

replacement). The 7951 Flow Computer will not power-up correctly if this battery is missing. If it is necessary to run the units without batteries for Intrinsic Safety reasons, then the battery should be replaced with a shorting disk inserted in the battery holder. Please consult the factory for further advice.

Replace the battery when the "Low Battery" system alarm is indicated. The procedure is in Chapter 14.

Contents

1. About this manual 1.1

1.1 What this manual tells you 1.1 1.2 Who should use this manual 1.1 1.3 Software versions covered by this manual 1.1

2. Getting started 2.1

2.1 What this chapter tells you 2.12.2 How to use this Chapter 2.1 2.3 The 7951 Inputs 2.2

2.3.1 Turbine flowmeter connections 2.3 2.3.2 Orifice flowmeter inputs 2.5 2.3.3 Liquid Density transducer connections (SAFE AREA ONLY) 2.8 2.3.4 Viscosity transducer connections 2.10 2.3.5 Temperature transmitter connections 2.12 2.3.6 Static pressure / Differential pressure transmitter connections 2.17 2.3.7 Digital (Status) Input connections 2.20

2.4 The 7951 Outputs 2.222.4.1 Pulse Output connections 2.23 2.4.2 Analog Output connections 2.24 2.4.3 Digital (Status) Output connections 2.25

2.5 Alarm Relay 2.262.6 Other 7951 Connections 2.26

2.6.1 Powering the 7951 2.26 2.6.2 Serial Port and Ethernet connections 2.27 2.6.3 Prover 2.27

3. About the 7951 3.1

3.1 Background 3.13.2 What the 7951 single-stream liquid turbine computer does 3.1 3.3 Physical description of the 7951 3.3 3.4 Typical installation 3.43.5 Checking your software version 3.4

4. Installing the system 4.1

4.1 What this chapter tells you 4.1 4.2 Hazardous and non-hazardous environments 4.1 4.3 Installation procedure 4.14.4 Step 1: Drawing up a wiring schedule 4.1 4.5 Step 2: Unpacking the instrument 4.2 4.6 Step 3: Setting DIP switches 4.3 4.7 Step 4: Fitting the 7951 4.44.8 Step 5: Making the external connections 4.6 4.9 Step 6: Earthing the instrument 4.6 4.10 Step 7: Connecting the power supply 4.7

5. The keyboard, display and indicators 5.1

5.1 What this Chapter tells you 5.1 5.2 The layout of the front panel 5.1 5.3 What the display shows 5.25.4 How the buttons work 5.25.5 Using the buttons to move around the menus 5.2 5.6 Using the buttons to view stored data 5.3 5.7 Using the buttons to edit information 5.4

5.7.1 Text editing 5.45.7.2 Multiple-choice option selection 5.5 5.7.3 Numerical editing 5.5 5.7.4 Data and time editing 5.6

5.8 The 7951 character set 5.75.9 LED indicators 5.75.8 Summary of button functions 5.8

6. The menu system 6.1

6.1 What this Chapter tells you 6.1 6.2 What the menu system does 6.1 6.3 How the menu system works 6.1

7. Serial Communications and Networking 7.1

7.1 What this chapter tells you 7.1 7.2 7951 Communication capabilities 7.1

7.2.1 Communication Ports 7.1 7.2.2 Data Services 7.1

7.3 MODBUS from the 7951 view-point 7.3 7.3.1 Introduction 7.37.3.2 Supported Commands 7.3 7.3.3 Floating Point Numbers 7.3 7.3.4 Word Swap Mode 7.3 7.3.5 Modbus addressing 7.4

7.4 Connecting the 7951 to an RS-232/RS-485 Link 7.5 7.4.1 RS-232 (full duplex) Rear Panel Pin Connections 7.5 7.4.2 RS-485 (half duplex) Rear Panel Pin Connections 7.6

7.5 After Connecting the 7951… 7.7 7.5.1 General RS-232C/485 Port Configuration 7.7 7.5.2 RS-232 Configuration 7.7 7.5.3 RS-485 Configuration 7.8

7.6 7951 Database access over a MODBUS network 7.9 7.6.1 Introduction 7.97.6.2 7951 Database information: software parameters values 7.11 7.6.3 7951 Database information: software parameter status 7.12 7.6.4 7951 Database information: full attributes 7.13

7.7 Historical Alarm Log access over a MODBUS network 7.16 7.7.1 Introduction 7.167.7.2 Worked Examples 7.17 7.7.3 Worked Example Two 7.17

7.8 Historical Event Log access over a MODBUS network 7.21 7.8.1 Introduction 7.217.8.2 Worked Examples 7.22

7.9 Archive access over a MODBUS network 7.25 7.9.1 Introduction 7.257.9.2 Worked Examples 7.26

7A. Addendum A: Peer-To-Peer Communications 7a.1

7B. Addendum B: High-speed List Communications 7b.1

7C Addendum C: 16-bit Communications (Gould List) 7c.1

7D Addendum D: ‘Intelligent Transmitter’ Monitor 7d.1

8. Alarms and Events 8.1

8.1 Alarms 8.1

8.1.1 Alarm types 8.18.1.2 Alarm indicators 8.1 8.1.3 How alarms are received and stored 8.1 8.1.4 Examining the Alarm Status Display and Historical Alarm Log 8.2 8.1.5 What the Alarm Status Display tells you 8.2 8.1.6 What the entries in the Historical Alarm Log tell you 8.3 8.1.7 Clearing all entries in the Historical Alarm Log 8.3 8.1.8 User-defined Alarms 8.4 8.1.9 Alarm Logger Output (ALO) 8.6 8.1.10 Alarm message list 8.7

8.2. Events 8.12

8.2.1 Introduction to 7951 events 8.12 8.2.2 Event indicators 8.12

8.2.3 How events are received and stored 8.12 8.2.4 Examining the Event Summary and the Event log 8.13 8.2.5 What the Event Status Display tells you 8.13 8.2.6 What the entries in the Historical Event Log tell you 8.13 8.2.7 Clearing all entries in the Historical Event Log 8.14

8.3. Enhanced Auditing 8.15

8.3.1 Audit User Events 8.15 8.3.2 Audit System Alarms 8.16 8.3.3 Audit Control Attributes 8.17 8.3.4 Audit Event Suppression Control: Automatic mode 8.19 8.3.5 Audit Alarm Suppression Control: Automatic mode 8.21

9. Additional facilities 9.1

9.1 Feature: Archiving 9.19.1.1 Introduction 9.19.1.2 Statistical information 9.2 9.1.3 Analysis of an archive 9.2 9.1.4 Configuration details 9.8 9.1.5 Re-sizing archive space 9.13 9.1.6 Operation details (Reporting) 9.14 9.1.7 Guided examples of archiving 9.17

9.2 Feature: PID Control 9.18

9.2.1 Overview 9.189.2.2 Configuration details 9.19

9.2 Feature: Printed Reports 9.20 9.3 Selecting units and data formats 9.22 9.4 Parameter alarm limits 9.229.5 Fallback values and modes 9.23 9.6 Units which the 7951 can display 9.23

10. Configuring using Wizards 10.1

10.1 Introduction to Wizards 10.110.2 Using Wizards 10.110.3 Quick-view Guide ( Set-up Wizards ) 10.3 10.4 Units Wizard selection 10.4

11. Configuring without using Wizards 11.1

11.1 What does this Chapter tell me? 11.1 11.2 Quick-find Index 11.211.3 A structured approach to configuring 11.3 11.4 Reference page conventions 11.5 11.5 Analogue inputs 11.611.6 Digital inputs 11.711.7 Pulse inputs 11.8

11.8 Turbine flow 11.911.9 Orifice flow metering (ISO 5167-1) 11.16

+ Orifice flow metering (AGA 3) 11.17 + Orifice flow metering (HART) 11.18

11.10 Coriolis flow metering 11.2811.11 Totalisers 11.3111.12 Prime ‘density loop’ fluid temperature 11.33 11.13 Prime ‘viscosity loop’ fluid temperature 11.34 11.14 Meter temperature 11.3511.15 ‘Density loop’ pressure 11.36 11.16 Meter pressure 11.3711.17 Header density 11.3811.18 API referred density 11.4411.19 4x5 matrix referred density 11.45 11.20 Meter density of known fluid 11.46 11.21 Base density of known fluid 11.47 11.22 Specific gravity / Degrees API 11.48 11.23 Special equations 11.4911.24 Header ‘viscosity loop’ density 11.50 11.25 Header viscosity 11.5211.26 Viscosity referral 11.5511.27 Base sediment & water measurements 11.57 11.28 Net oil/water measurements 11.59 11.29 Net oil/water flow rates and totals 11.65 11.30 Live analogue outputs 11.7311.31 Interface detection 11.7411.32 Digital outputs 11.7711.33 Live pulse outputs 11.7811.34 Passwords and security 11.79 11.35 Multi-page multi-view 11.81

12. Routine operation (Data maps) 12.1

12.1 Viewing the data 12.112.2 Checking the performance of the 7951 12.5 12.3 Printed reports 12.712.4 Giving your 7951 a tag number 12.10

13. Routine maintenance and fault-finding 13.1

13.1 Cleaning the instrument 13.1 13.2 Fault-finding 13.1

14. Removal and replacement of parts 14.1

14.1 Front panel assembly 14.114.2 Display 14.114.3 Switch panel 14.214.4 Processor board 14.314.5 Power supply board 14.314.6 Connector Board 14.314.7 Fuse 14.4

14.8 Back-up battery 14.514.9 Rear Panel Assembly 14.6

14.10 Mother Board 14.7

15. Assembly drawing and parts list 15.1

15.1 What the drawing and parts list tells you 15.1 15.2 How to obtain spare parts 15.1

16A. Flowmeter proving 16a.1

16A.1. Introduction to this Chapter 16a.1 16A.2 Provers and Pipe Proving Methods 16a.2

16A.2.1 Flowmeter Provers 16a.2 16A.2.2 Unidirectional Pipe Prover 16a.2 16A.2.3 Bi-directional Pipe Prover 16a.5 16A.2.4 Brooks Compact (Small Volume) Pipe Prover 16a.8

16A.3 Double-time Pulse Interpolation 16a.10 16A.4 The Prover Calculations 16a.11 16A.5 Connections: Inputs and Outputs 16a.16

16A.5.1 Status Inputs 16a.16 16A.5.2 Status Outputs 16a.19 16A.5.3 Analogue Inputs 16a.21 16A.5.4 Pulse (Turbine) Inputs 16a.21 16A.5.5 ‘Remote’ Proving Connection Summary 16a.21

16A.6 Valve Control and Monitoring 16a.22 16A.7 Configuration Tasks: Proving Details 16a.27 16A.8 Operating a Prove Session 16a.40 16A.9 Archiving of Proving Information 16a.51

16A.10 Prover Reporting 16a.53 16A.11 Trouble-shooting Guide 16a.56 16A.12 Miscellaneous Reference Information 16a.57

16B Master Meter Proving 16a.1

16B.1 What is the purpose if this Chapter? 16b.1 16B.2 Master meter proving (with a 7951 single-run flow computer) 16b.1 16B.3 Master Meter Proving Calculations 16b.3

16B.3.1 Volumetric Master Meter Proving of a Volumetric Meter (for Volume) 16b.3 16B.3.2 Volumetric Master Meter Proving of a Coriolis Mass Meter (for Mass) 16b.5 16B.3.3 Coriolis Mass Master Meter Proving a Coriolis Mass Meter (by Mass) 16b.6 16B.3.4 Coriolis Mass Master Meter Proving a Volumetric Meter (by Volume) 16b.7

16B.4 Input and output connections for master metering 16b.8 16B.5 Configuration Tasks: Proving Details 16b.11 16B.6 Operating a Prove Session 16b.20 16B.7 Archiving of Proving Information 16b.22 16B.8 Prover reporting 16b.24

17 HART, SMART, and the 7951 17.1

17.1 What this Chapter tells you 17.1 17.2 Introduction to SMART and HART with the 7951 17.1 17.3 Connecting the 7951 to a HART loop 17.3 17.4 Configuring the 7951 to use a HART loop 17.5 17.5 Post configuration – viewing HART data 17.7 17.6 SMART units of measurement 17.7

18. BATCHING (TRANSACTION) 18.1

18.1 Standard batch operations 18.1

18.1.1 Batch operation types 18.1 18.1.2 Batch operation parameter reference 18.3 18.1.3 Example 1: Manual batch type trigger 18.7 18.1.4 Example 2: Timed batches 18.8 18.1.5 Example 3: Quantity batch with FDC – Single program loop 18.9 18.1.6 Example 4: Quantity batch with FDC – Pause and resume controls 18.11 18.1.7 Example 5: Daily batch 18.13 18.1.8 Printed report samples 18.14

18.2 Retrospective batch total calculations 18.17

18.2.1 Overview 18.1718.2.2 Using retrospective calculations (on an archived record) 18.18 18.2.3 Using retrospective calculations (on the current batch record) 18.20

19. Flow Computer Basic Language (FC-BASIC) 19.1

19.1 Introduction 19.119.1.1 What is FC-BASIC? 19.1 19.1.2 What can FC-BASIC be used for? 19.1 19.1.3 What needs to be configured on the 7951 19.2

19.2 Editor commands 19.319.3 Command directory 19.3

19.3.1 Statements 19.319.3.2 Boolean expressions 19.6 19.3.3 Logical and bitwise operators 19.6 19.3.4 Relational operators 19.7 19.3.5 Arithmetic operators 19.7 19.3.6 Arithmetic functions 19.7 19.3.7 Pre-defined arrays 19.7 19.3.8 Pre-defined constants 19.8 19.3.9 Variable types 19.8 19.3.10 Direct 7951 database access 19.8

18.4 Sample FC-BASIC scripts 19.9 18.4.1 FC-BASIC Sample Script: AGA5 Algorithm 19.9 18.4.2 FC-BASIC Sample Script: Monthly Batch Report 19.11

AppendicesAppendix A Glossary A.1

Appendix B Blank wiring schedule B.1

Appendix C Technical data for the 7951 C.1

Appendix D Units and conversion factors D.1

Appendix E Data tables E.1

Appendix F Calculations F.1

Quick-start Guide

7951 2510 Page Q.1

Quick-start Guide

If you want to... Read....

Find out what's in this manual Contents pages

Get started quickly Chapter 2

Get an overview of the instrument Chapter 3 and Appendix C

Understand how the menu system works Chapter 6

Make connections to the instrument Chapters 2, 4 and Appendix C

Install the instrument and set it up Chapters 2, 4, 10 and 11

Operate the instrument Chapters 5 - 9 and 12

Carry out routine maintenance Chapter 13

Trace and repair faults Chapters 13 and 14

Remove and replace parts Chapters 14 and 15

know about flowmeter proving Chapter 16

know about HART support Chapter 17

know about Batching support Chapter 18

Understand what a term means Appendix A

Quick-start Guide

Page Q.2 7951 2510

Chapter 1 About this manual

7951 (Ch01/CA) Page 1.1

1. About this manual

1.1 What this manual tells you This manual tells you how to install, configure, operate, and service the 7951. In addition, some information is given to help you identify and correct some of the more common faults which may occur. However, since repairs are done by changing suspected faulty assemblies, fault-finding to board component level is not covered.

This manual assumes that all devices or peripherals to be connected to the 7951 have their own documentation which tells you how to install and configure them. For this reason it is assumed that anything which you want to link to the 7951 is already installed and working correctly in accordance with the manufacturer’s instructions.

Since the instrument can be used for a wide variety of purposes, it is driven by software specially for your application. This manual gives information about the software which applies to your machine only.

1.2 Who should use this manual This manual is for anyone who installs, uses, services or repairs the 7951.

1.3 Software version covered by this manual The software version dealt with in this manual is given on the title page. Chapter 3 tells you about the software is installed in your 7951.

Chapter 1 About this manual

Page 1.2 7951 (Ch01/CB)

Chapter 2 Getting started

7951 2510 (Ch02/CB) Page 2.1

2. Getting started

2.1 What this chapter tells you This chapter shows how to:

Connect different types of field instrumentation to a 7951.

Set the DIP switches in the 7951.

Select the appropriate software Wizard to configure the 7951.

Caution: Always refer to documentation supplied by the manufacturer for details of installing their equipment in a hazardous area. The 7951 is neither intrinsically safe nor explosion-proof, and can therefore only be used in a designated non-hazardous (safe) area.

Warning: Electricity is dangerous and can kill. Disconnect the power supply before making any connections or disassembling the 7951.

2.2 How to use this Chapter This chapter is divided into distinct sections:

Section 2.3 – this is for 7951 Inputs only.

Sections 2.4 and 2.5– these are for 7951 Outputs only.

Section 2.6 – this is for Other 7951 Connections, which includes powering the 7951.

These sections form a guide to connecting other field instrumentation to the 7951 unit. For example, Section 2.3.3 features a Liquid Density Transducer that uses the 7951’s Time Period Inputs (Density/Viscosity Inputs). Worked examples are provided to assist both new users and advanced users. Each worked example has a comprehensive set of instructions to establish a connection. Some types of connection may require DIP switches to be set. These switches are located inside the 7951, but only the Analog Input switches are accessible from holes on top of the housing. The Turbine Voltage Selection switch on the PSU Board is accessible only through removal of parts (see Chapter 14). Worked examples explain when and how to set a switch. For further information on DIP switches, see Chapter 4.


Page 2.2 7951 2510 (Ch02/CB)

2.3 The 7951 Inputs The following sub-sections deal with connections to external instrumentation that provide only inputs to the 7951.

Note: Use the “Health Check” facility on the 7951 to monitor what is being input. Refer to Chapter 12 to find out how to locate this facility using the menu system. Once located, select the particular type of input and then select the instance of that input to see what is happening.

Use this list to quickly locate appropriate examples:

Turbine flow meter connections......................................................Page 2.3

Orifice flow meter ..........................................................................Page 2.5

Liquid Density Transducer Connections (SAFE AREA ONLY)......Page 2.8

Viscosity Transducer Connections .................................................Page 2.10

Temperature Transmitter Connections ...........................................Page 2.12

Static Pressure / Differential Pressure Transmitter Connections....Page 2.17

Digital (Status) Input Connections ..................................................Page 2.20


7951 2510 (Ch02/CB) Page 2.3

2.3.1 Turbine flow meter connections

Support is provided for connecting 1 flow meter that outputs flow measurements in a pulse ‘train’ format. This flow meter must be connected to the Pulse Input on the rear panel of the 7951. The 7951 can accept single or dual pulse ‘trains’ through a Pulse Input. There are paired + and - pins for each pulse ‘train’ from the pick-up on the meter. (For technical data on the Pulse Input, see Appendix C.) The flow meter can be powered by using a specific pair of voltage supply pins on the rear panel of the 7951. These pins are an isolated supply source of either 8Vdc or 16Vdc. The voltage is selectable by a changing a single DIP-switch inside the 7951. (For information on locating this switch, see Chapter 4.)

Note: Software application use of a Pulse Input will depend on the particular release of the

software and the quantity of streams (metering-runs). For details on support and usage of this input, see Chapter 3.

For earthing arrangements, see Chapter 4 and Appendix C.

Example: A Turbine flow meter with dual pick-ups (i.e. dual pulse ‘trains’).

Follow these instructions to work through the example:

Turn off the power 1. Ensure that the 7951 is NOT powered up.

Set the voltage DIP switch

2. Select the voltage, 8Vdc or 16Vdc, which is required by the 7951 to power the turbine flow meter. This diagram shows the 8Vdc selection:

8V 16V

Connect the Turbine Flow Meter to the 7951

3. Wire the flow meter connections to the 7951 as shown in Figure 2.1 or Figure 2.2. If there is a single pick-up, use the ‘Pick-up A’ connections.

Turn on the power 4. Turn on the power to the system. The system goes through a Power On Self Test (POST) routine, which takes less than 30 seconds. When it is finished, ignore any flashing alarm lights which may appear.

Navigate to the Wizard selection menu

5. Press the MENU button to go immediately to Page 1 of the Main Menu (if you are not there already).

6. Press the DOWN-ARROW button to go to Page 2 of the menu.

7. Press the c button to select “Configure”.

8. Press the a button twice to go to the Wizard selection menu.

Select the Wizard 9. Press the b button, then use the UP-ARROW or DOWN-ARROW buttons to scroll through the option list until “Flow meter” is shown.

10. Press the b button to select “Flow meter”.

11. Press the c button to select “Turbine”.

Proceed with Wizard 12. Proceed with Wizard. Refer to chapter 10 for a general guide to Wizards. Refer to Chapter 11 for ‘fine-tuning’ the configuration.


Page 2.4 7951 2510 (Ch02/CB)

7951 D-type

(1) Power Supply Inputs. (2) Pick-up A. (3) Pick-up B.

Figure 2.1: Typical dual-pickup turbine flow meter (7951 D-type connections)

7951 Klippon

(1) Power Supply Inputs. (2) Pick-up A. (3) Pick-up B.

Figure 2.2: Typical dual-pickup turbine flow meter (7951 Klippon connections)


7951 2510 (Ch02/CB) Page 2.5

2.3.2 Orifice flow meter connections

Support is provided for connecting 1 flow meter that comprises 2 DP cells outputting measurements in a 4-20mA format. This DP cells must be connected to one of the Analog Inputs on the rear panel of the 7951. (For technical data on Analog Inputs, see Appendix C.)

Note: Software application use of an Analog Input will depend on the particular release of the

software. For details on support and usage of this input, see Chapter 3.


Analog Inputs 1 to 4

Analog Inputs 1 to 4 have a dual purpose. They can be individually changed to be a PRT Input or a mA Input. This is achieved by setting the DIP switches that are accessible through the holes on top of the housing.

Analog Input 5 onwards

Analog Inputs 5 and onwards are all mA-type inputs.

Note: Care is needed when preparing to connect a mA-type flow meter:

If using any of Analog Inputs 1 to 4, the individual DIP-switch of the input must be set to “mA” and not “PRT” (see example). For Analog Inputs 5 and onwards, this does not apply.

Ensure that only the Analog Power pins are used to power the flow meter. (The reason for this is that PRT Power is only applied when a measurement is required and, therefore, not suitable for loop powered mA devices.)

Example 1: 2 off DP cells connected to Analog Inputs 1 and 2.



Set DIP-switches 2. Ensure that the DIP-switch for Analog Input 1 is set for “mA”.

3. Ensure that the DIP-switch for Analog Input 2 is set for “mA”.

If inputs 3 or 4 were to be used instead, the DIP-switch of those inputs needs to be set to “mA”. For inputs 5 and onwards, the DIP-switches do not apply.

Connect the flow meter to the 7951

3. Wire the 1st cell to Input 1 the 7951 as shown in Figure 2.3 or Figure 2.4.

4. Wire the 2nd cell to Input 2 the 7951 as shown in Figure 2.3 or Figure 2.4.

Turn on the power 5. Turn on the power to the system. The system goes through a Power On Self Test (POST) routine which takes less than 30 seconds. When it is finished, ignore any flashing alarm lights which may appear.


6. Press the MENU button to immediately go to Page 1 of the Main Menu (if you aren’t there already).




Page 2.6 7951 2510 (Ch02/CB)

Select the Wizard 9. Press the b button, then use the UP-ARROW or DOWN-ARROW buttons to scroll through the option list until “Flow meter” is shown.

10. Press the b button to select “Flow meter”.

11. Press the c button to select “Orifice”.


7951 D-type

Note: Choose one analog input for each device. See Table 2.1 for connections to analog inputs 5 and onwards.

Figure 2.3: a 4-20mA transmitter (7951 D-type connections)

7951 Klippon


Figure 2.4: a 4-20mA transmitter (7951 Klippon connections)


7951 2510 (Ch02/CB) Page 2.7

Table 2.1: Analog Inputs 5 to 10 (7951 D-type only)

Connections Analog I/P 5 Analog I/P 6 Analog I/P 7

Analogue Power (+) SK8/12 SK8/24 SK8/24

Signal (+) SK8/9 SK8/14 SK8/16

Signal (-) SK8/10 SK8/15 SK8/17

Analogue Power (-) SK8/13 SK8/25 SK8/25



Signal (+) SK8/18 SK8/20 SK8/22

Signal (-) SK8/19 SK8/21 SK8/23


Table 2.2: Analog Inputs 5 to 8 (7951 Klippon only)

Connection Label Analog I/P 5 Analog I/P 6 Analog I/P 7 Analog I/P 8

Analogue Power (+) PL9/5 PL9/5 PL9/5 PL9/5

Signal (+) PL9/2 PL9/6 PL7/9 PL8/9

Signal (-) PL9/3 PL9/7 PL8/10 PL8/10

Analogue Power (-) PL9/8 PL9/8 PL9/8 PL9/8


Page 2.8 7951 2510 (Ch02/CB)

2.3.3 Liquid Density Transducer Connections (SAFE AREA ONLY)


Support is provided for connecting 2 frequency output transducers. The density measurement (+ and - signal) from the transducer must be connected to a Density/Viscosity Input (Time Period Input) on the 7951. (For technical data on these inputs, see Appendix C.) Each transducer can be powered by using the voltage supply pins on the 7951. These voltage pins utilise the 7951’s isolated power supply. (For technical data on the 7951’s voltage supplies, see Appendix C.) If the transducer has an integrated PT100 sensor and it is to be connected to the 7951, see Section 2.3.5 for a worked example. For illustration purposes, the integrated PT100 of a single 7835/45/46/47 transducer is shown in the connection diagrams of this section.

Note: Software application use of a Density/Viscosity Input will depend on the particular

release of the software. For details on usage of this input, see Chapter 3.


Example: A Standard 7835/45/46/47 Liquid Density Transducer (with integrated PT100 sensor).



Connect the density transducer(s) to the 7951

2. Wire the frequency output transducer to the 7951 as shown in Figure 2.5 or Figure 2.6. When there is one transducer, use Time Period Input 1.







Select the Wizard 8. Press the b button, then use the UP-ARROW or DOWN-ARROW buttons to scroll through the option list until “Txdr density” is shown.

9. Press the b button to select “Txdr density”.



7951 2510 (Ch02/CB) Page 2.9

7951 D-type

Notes: Choose one time period input. Analog Inputs 1 to 4 are individually selectable to be either a PRT Input or a mA Input by means of a DIP switch.

Figure 2.5: 7835/45/46/47 density transducer (7951 D-type connections)

7951 Klippon


Figure 2.6: 7835/45/46/47 density transducer (7951 Klippon connections)


Page 2.10 7951 2510 (Ch02/CB)

2.3.4 Viscosity Transducer Connections (SAFE AREA ONLY)


Support is provided for connecting 2 frequency output transducers. The viscosity measurement (+ and - signal) from the transducer must be connected to a Density/Viscosity Input (Time Period Input) on the 7951. (For technical data on these inputs, see Appendix C.) Each transducer can be powered by using the voltage supply pins on the 7951. These voltage pins utilise the 7951’s isolated power supply. (For technical data on the 7951’s voltage supplies, see Appendix C.) If the transducer has an integrated PT100 sensor and it is to be connected to the 7951, see Section 2.3.5 for a worked example. For illustration purposes, the integrated PT100 of a 7827 transducer is shown in the connection diagrams of this section.

Note: Software application use of a Density/Viscosity Input will depend on the particular

release of the software. For details on usage of this input, see Chapter 3.


Example: A 7827 Viscosity Transducer (with integrated PT100 sensor)



Connect the viscosity transducer(s) to the 7951

2. Wire the transducer to the 7951 as show in Figure 2.7 or Figure 2.8. When there is one transducer, use Time Period Input 3.







Select the Wizard 8. Press the b button, then use the UP-ARROW or DOWN-ARROW buttons to scroll through the option list until “Viscosity” is shown.

9. Press the b button to select “Viscosity”.



7951 2510 (Ch02/CB) Page 2.11

7951D-type


Figure 2.7: 7827 viscosity transducer (7951 D-type connections)

7951 Klippon


Figure 2.8: 7827 viscosity transducer (7951 Klippon connections)


Page 2.12 7951 2510 (Ch02/CB)

2.3.5 Temperature Transmitter Connections

Support is provided for connecting PT100 (PRT) and 0/4-20mA temperature transmitters to the Analog Inputs on the 7951. (For technical data on Analog Inputs, see Appendix C.) Analog Inputs 1 to 4

Analog Inputs 1 to 4 have a dual purpose. They can be individually changed to be a PRT Input or a mA Input. This is achieved by setting the DIP-switches that are accessible through the holes on top of the housing. Analog Inputs 5 and onwards Analog Inputs 5 and onwards are all mA-type inputs.

Note: Software application use of an Analog Input will depend on the particular release of the

software. For details on usage of this input, see Chapter 3.


0/4-20mA-type transmitter

Care is needed when preparing to connect a mA-type transmitter:

If using any of Analog Inputs 1 to 4, the individual DIP-switch of the input must be set to “mA” and not “PRT” (see example). For Analog Inputs 5 and onwards, this does not apply.

Ensure that only the Analog Power pins are used. (The reason for this is that PRT Power is only applied when a measurement of temperature is required and, therefore, not suitable for loop powered mA devices.)

See Example 1 on page 2.6. PRT-type transmitter

Care is needed when preparing to use a PRT-type transmitter:

Only Analog Inputs 1 - 4 can support PRT-type transmitters. The individual DIP switch of the Analog Input must be set to “PRT” and not “mA” (see example).

Ensure that only the PRT Power pins are used.

See Example 2 on page 2.15.


7951 2510 (Ch02/CB) Page 2.13

Example 1: a 4-20mA temperature transmitter



Set DIP switches 2. If Analog Input 1, 2, 3 or 4 is to be used, the DIP-switch of that Analog Input needs to be set to “mA”.

For example, if using Analog Input 1, set the DIP-switch as shown here.

(For Analog Inputs 5 and onwards, the DIP-switch does not apply.)

Connect the temperature transmitter

3. Wire the connections to the 7951 as shown in Figure 2.9 or Figure 2.4.


Navigate to the Wizards selection menu





Select the Wizard 9. Press the b button, then the UP-ARROW or DOWN-ARROW buttons to scroll through the option list until “Temperature” is shown.

10. Press the b button to select “Temperature”.


7951 D-type




Page 2.14 7951 2510 (Ch02/CB)

7951 Klippon



Table 2.3: Analog Inputs 5 - 10 (7951 D-type only)




Signal (-) SK8/10 SK8/15 SK8/17




Signal (+) SK8/18 SK8/20 SK8/22

Signal (-) SK8/19 SK8/21 SK8/23


Table 2.4: Analog Inputs 5 - 8 (7951 Klippon only)




Signal (-) PL9/3 PL9/7 PL8/10 PL8/10



7951 2510 (Ch02/CB) Page 2.15

Example 2: a PT100 (PRT-type)



Set DIP switches 2. Only Analog Inputs 1 - 4 can support PRT-type transmitters.

The DIP switch needs to be set to “PRT”.

For example, if using Analog Input 1, set the DIP switch as shown here.

Connect the temperature transmitter

3. Wire the connections to the 7951 as shown in Figure 2.2.11 or Figure 2.12.







Select the Wizard 9. Press the b button, then the UP-ARROW or DOWN-ARROW buttons to scroll through the option list until “Temperature” is shown.

10. Press the b button to select “Temperature”.


7951 D-type

Note: Choose one of these analog inputs. Only the first four Analog Inputs can support PT100 (PRT-type) transmitters

Figure 2.2.11: a PT100 (PRT-type) transmitter (7951 D-type connections)


Page 2.16 7951 2510 (Ch02/CB)

7951 Klippon

Note: Choose one of these analog inputs. Only the first four Analog Inputs can support PT100 (PRT-type) transmitters

Figure 2.12: a PT100 (PRT-type) transmitter (7951 Klippon connections)


7951 2510 (Ch02/CB) Page 2.17

2.3.6 Static Pressure / Differential Pressure Transmitter Connections

Support is provided for connecting 0/4-20mA pressure transmitters to the Analog Inputs on the 7951. (For technical data on Analog Inputs, see Appendix C.) Analog Inputs 1 to 4

Analog Inputs 1 to 4 have a dual purpose. They can be set to a PRT-type Input or a mA-type Input. This is achieved by setting the DIP switches that are accessible through the holes on top of the housing. For static pressure and differential pressure transmitters, only the “mA” option applies. Analog Inputs 5 and onwards

Analog Inputs 5 and onwards are all mA-type inputs.

Note: Software application support and use of an Analog Input will depend on the particular

release of the software. For details on support and usage of this input, see Chapter 3.


If there is more than one differential pressure transmitter, they must be connected to a series of Analog Inputs. For example, if transmitter ‘DP1’ uses Analog Input 5, then transmitter ‘DP2’ must use Analog Input 6, and so on.

Care is needed when preparing to connect a mA-type transmitter:

If using any of Analog Inputs 1 to 4, the individual DIP switch of the input must be set to “mA” and not “PRT” (see example). For Analog Inputs 5 and onwards, this does not apply.

Ensure that only the Analog Power pins are used. (The reason for this is that PRT Power is only applied when a measurement of temperature is required and, therefore, not suitable for loop powered mA devices.)

See Example on page 2.18.


Page 2.18 7951 2510 (Ch02/CB)

Example: a 4-20mA static pressure transmitter, powered by the 7951 (24V isolated supply).



Set DIP switches 2. If Analog Input 1, 2, 3 or 4 is to be used, the DIP-switch of that Analog Input needs to be set to “mA”.

For example, if using Analog Input 1, set the DIP-switch as shown here.

(For Analog Inputs 5 and onwards, the DIP-switch does not apply.)

Connect the transmitter(s)

3. Wire the connections to the 7951 as shown in Figure 2.13 or Figure 2.14.







Select the Wizard 9. Press the b button, then the UP-ARROW or DOWN-ARROW buttons to scroll through the option list until “Pressure” is shown.

10. Press the b button to select “Pressure”.


7951 D-type




7951 2510 (Ch02/CB) Page 2.19

7951 Klippon



Table 2.5: Analog Inputs 5 - 10 (7951 D-type only)




Signal (-) SK8/10 SK8/15 SK8/17




Signal (+) SK8/18 SK8/20 SK8/22

Signal (-) SK8/19 SK8/21 SK8/23


Table 2.6: Analog Inputs 5 - 8 (7951 Klippon only)




Signal (-) PL9/3 PL9/7 PL8/10 PL8/10



Page 2.20 7951 2510 (Ch02/CB)

2.3.7 Digital (Status) Input Connections

Digital (Status) Inputs are available on the 7951 for connection to field instrumentation such as on/off switches. Status Inputs 1 and 2 are special “fast” versions for use with a pipe-based Flow Meter Prover – see Chapter 16A/16B. (For technical data on Digital Inputs, see Appendix C.)

Note: Software application support and use of Digital (Status) Inputs will depend on the particular

release of the software. For details on support and usage of this input, see Chapter 3.

Digital Inputs on the 7951 are commonly referred to as Status Inputs.

Figure 2.15 and Figure 2.16 show methods for wiring up a switch to a Digital (Status) Input on a 7951 D-type unit:

Circuit operation notes: A closed switch produces a digital signal that represents a value of 1. An open switch produces a digital signal that represents a value of 0.

Figure 2.15: Internally Powered Status Inputs (7951 D-type)

Note: To maintain electrical isolation, use an isolated voltage supply.

Figure 2.16: Externally Powered Status Inputs (7951 D-type)


7951 2510 (Ch02/CB) Page 2.21

Figure 2.17 and Figure 2.18 show methods for wiring up a switch to a Digital (Status) Input on a 7951 Klippon unit: Circuit operation notes: A closed switch produces a digital signal that represents a value of 1.

An open switch produces a digital signal that represents a value of 0.

Figure 2.17: Internally Powered Status Inputs (7951 Klippon)

Note: To maintain electrical isolation, use an isolated voltage supply.

Figure 2.18: Externally Powered Status Inputs (7951 Klippon)


Page 2.22 7951 2510 (Ch02/CB)

2.4 7951 Outputs The following sub-sections cover connections with external instrumentation that expect outputs from the 7951.

Note: Use the “Health Check” facility on the 7951 to monitor what is being output. Refer to Chapter 12 to find out how to locate this facility using the menu system. Once located, select the particular type of output and then select the instance of that output to see what is happening.

Use this list to quickly locate appropriate examples:

Pulse Output Connections ...........................................................Page 2.23

Analog Output Connections.........................................................Page 2.24

Digital (Status) Output Connections.............................................Page 2.25


7951 2510 (Ch02/CB) Page 2.23

2.4.1 Pulse Output Connections

Pulse Outputs are available on the 7951 for connection to instrumentation such as an electronic counter. Figure 2.19 and Figure 2.20 show how to wire up a relay to the Pulse Outputs on a 7951.

Note: Software application support and use of Pulse Outputs will depend on the particular

release of the software. For details on support and usage of this output, see Chapter 3.

For technical data on Pulse Outputs, see Appendix C.

Note: The power can be taken from an external supply or from voltage supply pins on the 7951.

Figure 2.19: Pulse Outputs (7951 D-type)

Note: The power can be taken from an external supply or from voltage supply pins on the 7951.

Figure 2.20: Pulse Outputs (7951 Klippon)


Page 2.24 7951 2510 (Ch02/CB)

2.4.2 Analog Output Connections

Support is provided for connecting instrumentation such as a chart recorder to the Analog Outputs on a 7951.

Note: Software application support and use of Pulse Outputs will depend on the particular

release of the software. For details on support and usage of this output, see Chapter 3.

The Analog Outputs are powered by the 7951.

For technical data on Analog Outputs, see Appendix C.

Figure 2.21 and Figure 2.22 show how to wire up instrumentation to the Analog Outputs on the 7951:

Note: Analog Outputs 5 to 8 are enabled only if the extra I/O option was chosen –

see Appendix C for information on hardware options.

Figure 2.21: Analog Outputs (7951 D-type)

Note: Analog Outputs 5 to 8 are enabled only if the extra I/O option was chosen –

see Appendix C for information on options.

Figure 2.22: Analog Outputs (7951 Klippon)


7951 2510 (Ch02/CB) Page 2.25

2.4.3 Digital (Status) Output Connections

Digital (Status) Outputs are available on the 7951 for connection to instrumentation such as a user-selected relay.

Note: Software application support and use of Digital (Status) Outputs will depend on the

particular release of the software. For details on support and usage of this output, see Chapter 3.

For technical data on Digital (Status) Outputs, see Appendix C.

Digital Outputs on the 7951 are commonly referred to as Status Outputs.

Status Output 1 is the Alarm Relay output – see Section 2.5 for this type of connection.

Figure 2.23 and Figure 2.24 show how to wire a user-selected relay to a Digital (Status) Output on a 7951:

(1) External power supply provides voltage and current suitable for user-selected relay.

(2) The diode protects the 7951 against reverse voltages.

Figure 2.23: Status Outputs (7951 D-type)

(1) External power supply provides voltage and current suitable for user-selected relay.

(2) The diode protects the 7951 against reverse voltages.

Figure 2.24: Status Outputs (7951 Klippon)


Page 2.26 7951 2510 (Ch02/CB)

2.5 Alarm Relay

Note:

For technical details on the Relay output, see Appendix C.

For earthing arrangements on the 7951, see Chapter 4 and Appendix C.

The Alarm Relay output is sometimes referred to as Status Output 1.

7951 D-type

There are 2 contacts: 1: Either “Normally Open” pin SK4/12 or “Normally Closed” pin SK4/25. 2: “Alarm Common” pin SK4/13. 7951 Klippon

There are 2 contacts: 1: Either “Normally Open” pin PL2/8 or “Normally Closed” pin PL2/10. 2: “Alarm Common” pin PL2/9. This relay output is powered by the 7951, and functions as a ‘watchdog’ for indicating the presence of at least one active alarm. The Normally Open (NO) contact is energised only while there is an active alarm. The Normally Closed (NC) contact is energised while there is no active alarm. Turn to Chapter 8 for a full guide to the ALARM LOGGER OUTPUT (ALO) feature, which uses the Digital (Status) outputs and this Relay output.

2.6 Other 7951 Connections 2.6.1 Powering the 7951

Switch-off the 24Vdc external power supply before connecting it, and the cable’s screen, to the terminals of PL1. Then make the connections as shown in Figure 2.25. When ready, apply the power to start-up the 7951. (There is no On/Off switch on the 7951).

Note:

For technical details on the power input and the power outputs, see Appendix C.

For earthing arrangements on the 7951, see Chapter 4 and Appendix C.

Figure 2.25: DC Power Input (PL1)


7951 2510 (Ch02/CB) Page 2.27

2.6.2 Serial Port and Ethernet Communications

Turn to Chapter 7 for a full guide to Serial Port and Ethernet Port Communications involving the 7951.

2.6.3 Prover

Turn to Chapter 16A/16B for a full guide to Flow Meter Proving and Master Meter Proving with a 7951.


Page 2.28 7951 2510 (Ch02/CB)

Chapter 3 About the 7951

7951 2510 (Ch03/BA) Page 3.1

3. About the 7951

3.1 Background The 7951 is designed to meet the demand for a reliable, versatile, user-friendly and cost-effective instrument for liquid and gas metering. It has a Motorola 68332 32-bit microprocessor and surface-mounted circuit board components so that it is powerful, reliable and compact.

Features of the 7951 include:

o An intuitive menu system (for easy access to information).

o Comprehensive interrogation facilities.

o Alarm and alarm history facilities.

o Events and event history facilities.

o NEMA12, IP52 panel mounted case.

o Dc powered.

o Three serial ports (using RS232 or RS485) for MODBUS communications, and printing.

3.2 What the 7951 single-stream liquid flow computer does The 7951 single-stream liquid flow computer is used specifically with liquid products and may use a number of types of flow meter (such as turbine, orifice or venturi meters) to measure parameters of interest.

The liquid flow computer software has support for connecting:

o Up to two† single/dual pulse turbine flow meters..........................................................................(Chapter 2)

o Up to two liquid density transducers - 7830, 7835, 7840, and 7845 models only .......................(Chapter 2)

o Up to four PT100 or 0/4-20mA type temperature transmitters.....................................................(Chapter 2)

o Up to two 0/4-20mA type static pressure transmitters..................................................................(Chapter 2)

o A conventional pipe Prover‡ (Unidirectional, Bi-directional, or Brooks Compact Prover)......... (Chapter 16)

o Stream Block valve and Prover valves ...................................................................................... (Chapter 16)

o Coriolis mass flow meter (HART Input or mA-type Analogue Input)....................................(Chapters 2, 17)

In this application, the main purpose of the 7951 is to calculate flow rates and flow totals:

o Indicated volume flow rate and flow total (Pulse flow meter only)............................................. (Chapter 11)

o Indicated standard volume flow rate and flow total (Pulse flow meter only) ............................. (Chapter 11)

o Gross volume flow rate and flow total........................................................................................ (Chapter 11)

o Gross standard volume flow rate and flow total......................................................................... (Chapter 11)

o Mass flow rate and flow total...................................................................................................... (Chapter 11)

o Nett volume flow rate and flow total (Pulse flow meter only)..................................................... (Chapter 11)

o Corrected mass flow rate and flow total (Pulse flow meter only) .............................................. (Chapter 11)

† A 7951 with Klippon connectors can support one pulse (turbine) flow meter. ‡ This requires a 7951 with a D-type rear panel and an add-on board providing extra Status Inputs and Outputs.


Page 3.2 7951 2510 (Ch03/BA)

It can also generate:

o Line pressure – from HART Input or Analogue Input. .................................................................(Chapter 11)

o Line temperature – from HART Input or Analogue Input.............................................................(Chapter 11)

o Density-loop temperature – from HART Input or Analogue Input ...............................................(Chapter 11)

o Line density – from a density transducer, HART Input, or from base density.............................(Chapter 11)

o Base density – from matrix referral calculation, or from API calculation§ ...................................(Chapter 11)

o Specific gravity – from an analogue input ..................................................................................(Chapter 11)

o Meter factor – from flow meter proving, or a user-definable calibration curve............................(Chapter 11)

o CTL (Temperature correction factor) – from API calculation.......................................................(Chapter 11)

o CPL (Pressure correction factor) – from API calculation.............................................................(Chapter 11)

o Prover inlet temperature and pressure – from HART Input or Analogue Input...........................(Chapter 11)

o Prover outlet temperature and pressure – from HART Input or Analogue Input. .......................(Chapter 11)

Other application features:

o Alarm summary and history log ....................................................................................................(Chapter 8)

o Event summary and history log ....................................................................................................(Chapter 8)

o Data Logging and Archiving..........................................................................................................(Chapter 9)

o Net oil/water calculations ............................................................................................................(Chapter 11)

o Special equation 1.......................................................................................................................(Chapter 11)

o Special equation 2.......................................................................................................................(Chapter 11)

o Security and passwords..............................................................................................................(Chapter 11)

o Flow meter proving**

(including automatic/manual valve control, and a prover report) ...............................................(Chapter 16)

o Batching ......................................................................................................................................(Chapter 18)

o Retrospective calculations ..........................................................................................................(Chapter 18)

§ API calculation complies with section 11.2.1 and 11.2.2 of API standard (September 1996 draft copy). ** This requires a 7951 with a D-type rear panel, and an add-on board providing extra Status Inputs and Status Outputs.


7951 2510 (Ch03/BA) Page 3.3

3.3 Physical description of the 7951The main body of the 7951 is a one-piece aluminium extrusion which provides the best possible EMC protection. The keyboard and display is attached to the front of the instrument and all electrical and communications connectors are mounted on the Rear Panel. The 7951 is available with two types of rear Panel - one with Klippon connectors, the other with D-type connectors.

The case contains four circuit boards. The Processor Board and the Power Supply Board are mounted horizontally. These are connected by plugs and sockets to the Mother Board which is mounted vertically at the back of the case. The Connector Board is parallel to the Mother Board to which it is joined.

The Keyboard and Display are wired to the Processor Board. The Connector Board holds the connectors to which external devices are linked.

Keyboardand display

PL1

SK3

SK2

SK1

SK4 SK5 SK6 SK7 SK8

SK1

SK2

SK3

PL1PL2 PL3 PL4 PL5 PL6 PL7 PL8 PL9

Either... Klippon connectors

Or... D-type connectors

Two types ofRear Panel

ConnectorBoard

PowerSupplyBoard

MotherBoard

ProcessorBoard

Figure 3.1: The 7951 and its major assemblies


Page 3.4 7951 2510 (Ch03/BA)

3.4 Typical installation The diagram below illustrates a typical installation of a liquid turbine metering system that utilises the 7951 Liquid Flow Computer.

PeriodicTimeP T

7951 FLOW COMPUTER

7835 Densitometer

PRT or4-20mA 4-20mA

Pulse 'B'

Pulse 'A'

4-20mA outputs

Serial comms.

Pulse outputs

Status outputs

Figure 3.2: Typical application using a 7951

3.5 Checking your software version The 7951 is driven by pre-loaded software which differs according to the application for which the instrument is to be used. To check hardware configuration, see Ordering Information in Appendix C.

PREFIX DIGIT 1 DIGIT 2 DIGIT 3 DIGIT 4

SOFTWARE VERSION NUMBER

DIGIT 2:

FLOW METER

0 NONE 1 ORIFICE 2 TURBINE/PD 3 VENTURI 4 MASS 5 MULTI

DIGIT 4:

SPECIAL

0 – 9

PREFIX:

HARDWARE PLATFORM

51 7951 55 7955

DIGIT 1:

METERED PRODUCT

1 GAS 2 LIQUID 3 BOTH 4 OTHER

DIGIT 3:

STREAMS/ CHANNELS

1 SINGLE 2 DUAL 3 TRIPLE 4 QUAD 5 1, 2, 3 or 4

Figure 3.3: Software version number

For example, for a 7951 Single-Stream Liquid Flow Computer, the software version number is 512510.You can find the software version number in two ways:

1. It is printed on a label at the rear panel of the 7951.

2. It is written into the menu structure – see Chapter 12.

Chapter 4 Installing the system

7951 (Ch04/DA) Page 4.1

4. Installing the system

4.1 What this chapter tells you This chapter gives full instructions for installing the 7951.

It does not go into detail about how to install any peripheral devices (such as transducers, computers or printers) which are connected to the 7951. For this information you must refer to the documentation supplied with these items.

4.2 Hazardous and non-hazardous environments

Caution:Always refer to documentation supplied by the manufacturer for details of installing their equipment in a hazardous area. The 7951 is neither intrinsically safe nor explosion-proof. and can therefore only be used in a designated non-hazardous (safe) area.

If all or part of an installation is in an area where there is the risk of fire or explosion (which is almost always the case when gases are involved), then safety barriers or galvanic isolators usually have to be wired into the circuit. However, some instruments are explosion-proof and barriers are not, therefore, needed.

4.3 Installation procedure Briefly, the procedure is:

Step 1: Draw up a wiring schedule.

Step 2: Unpack the 7951.

Step 3: Set the DIP switches.

Step 4: Fit the 7951.

Step 5: Make all external connections.

Step 6: Earth the installation.

Step 7: Connect power supply.

The steps in the procedure are explained in the following sections.

4.4 Step 1: Drawing up a wiring schedule Before you make any connections, you must draw up a wiring schedule to help you identify wiring colours and make sure that you do not connect more items of any given type than are allowed. (If you are in doubt, check the specification in Appendix C.)

A blank copy of a wiring schedule is given in Appendix B.


Page 4.2 7951 (Ch04/DA)

4.5 Step 2: Unpacking the instrument Remove the instrument from its packing and examine it to see if any items are loose or if it has been damaged in transit. Check that all items on the shipping list are present. If any items are missing or if the equipment is damaged, contact your supplier immediately for further advice.

Note: If you have ordered an option card, this is already installed in the 7951.

Table 4.1: What should be supplied with the 7951 (Klippon)

Item Quantity

Mounting Clamp Assembly 1

Captive screws 2

Mounting strap 1

Location moulding 1

Socket identification label 1

9-way D-type plugs 3

9-way connector hoods 3

4-way socket 1

10-way sockets 8

2 Amp glass fuse (this is a spare) 1

Table 4.2: What should be supplied with the 7951 (D-type)

Item Quantity

Mounting Clamp Assembly 1

Captive screws 2

Mounting strap 1

Location moulding 1


9-way D-type connector hoods 3


25-way D-type connector hoods 5

4-way socket 1

2 Amp ceramic fuse (this is a spare) 1


7951 (Ch04/DA) Page 4.3

4.6 Step 3: Setting DIP-switches Some types of connection may require DIP-switches to be set.

4.6.1 Analogue Input DP-switches The 7951 has two blocks of DIP-switches on the Processor Board, as shown in Figure 4.1:

SW1 switches – select whether each input is 4-20 mA or PRT.

SW2 switches – not used in the current version of 7951.

The setting of each switch in the SW2 block must be the same as the corresponding pair of switches in the SW1 block. The 7951 may not work correctly otherwise.

The 7951 is supplied with the DIP-switches in these default settings:

Input 1 PRT

Inputs 2-4: 4-20mA

Part of the 7951Processor Board

1

2

3

A

B

C

4D

SW2

SW1

PRT4-20mA

Figure 4.1: DIP-switches on the Processor Board

If you want to change the Analog Input switch settings, you must also configure the inputs. This is explained in chapter 11. After the configuration has been completed, the 7951 should be switched into the 'secure' mode to prevent unauthorised or accidental tampering with the instrument's configuration.

Note: The 7951 is always shipped from the factory with the security lock on the front panel set

to the ‘non-secure’ mode.

4.6.2 Turbine Voltage Selection switches

The Turbine Voltage Selection switch is a DIP switch on the PSU Board, which is accessible through removal of parts (see Chapter 14). Choose between 8 volts dc or 16 volts dc for all flow meters powered by the 7951. The 7951 is shipped with the switch set for 8 volts dc.

For flow meter connection details, see chapter 2.


Page 4.4 7951 (Ch04/DA)

4.7 Step 4: Fitting the 7951Caution: You must not fit the 7951 where it may be subjected to extreme conditions or be liable to damage. For further information about the environmental conditions within which it can operate, see Appendix C.

1. Firstly, referring to Figure 4.4.2, cut out an aperture in the front panel for each instrument which is to be mounted on it.

Aperture for theinstrument



29±1mm

17±1mm

14.5mm

17.5mm192±1mm

96±1mm Aperture for theinstrument

Figure 4.4.2: Minimum dimensions for a panel with apertures to fit four 7951’s

2. Each instrument is mounted in a clamp which is fixed to the rear of the front panel, as shown in the two diagrams that follow.

MountingClamp

The 7951 unit

LocationMoulding

278.7mm

101mm

Panel withaperture

3mm

Figure 4.4.3: Before assembly

256mm12.5mm

7.2mm

10mm

3mm

CaptiveClamp

Screws (2) Rear Panelof 7951

MountingClamp

113mm

221mm

Note: Sufficient clearance is required for plugs and cables at the rear of the 7951

Figure 4.4: After assembly


7951 (Ch04/DA) Page 4.5

You can mount the clamp so that it is fixed permanently or can be removed later, if required. If you want the clamp to be fixed permanently, carry out Steps 3 - 8. If you want to be able to remove the clamp, carry out Steps 9 - 12.

If the clamp is to be fixed permanently:

1. Make sure that the face of the front panel is in good condition and has no loose or flaking paint. Use a suitable de-greasing agent to clean the face of the panel.

2. Insert the location moulding through the aperture in the front panel.

3. Peel the protective strip off the adhesive tape on the face of the mounting clamp. Then, working from the back of the front panel, carefully position the clamp over the location moulding. The clamp and panel bond on contact.

4. Press firmly on the area where the clamp is bonded to the front panel to ensure that they are bonded firmly. Remove the Location Moulding and discard it.

5. Slide the instrument through the front panel. Tighten the two captive screws to secure it into the clamp.

6. Finally, attach all connectors to the back panel.

Note that, if you install more than one instrument, it helps to support them if you use a Mounting Strap to link each clamp to the next one, as shown in Figure 4.5:

Back ofinstrument

Back ofinstrument

Mountingstrap

Mounting clamp Mounting clamp

Inside offront panel

Figure 4.5: Mounting arrangements for more than one instrument

If the clamp is to be removable:

7. Insert the location moulding through the aperture in the front panel.

8. Working from the back of the front panel, carefully position the clamp over the location moulding. Remove the Location Moulding and discard it.

9. Slide the instrument through the front panel. Tighten the two captive screws to secure it into the clamp.

Note that, if you install more than one instrument, it helps to support them if you use a Mounting Strap to link each clamp to the next one, as shown in the diagram.


Page 4.6 7951 (Ch04/DA)

4.8 Step 5: Making the external connections 1. Refer to the documentation supplied with the external equipment to see if it is necessary to carry out

any special procedures when connecting them to the 7951. Take special notice of any information about safety requirements in hazardous areas, and complying with EMC regulations. To meet the EC Directive for EMC (Electromagnetic Compatibility), it is recommended that the Flow Computer be connected to transducers using a suitable instrumentation cable containing individually shielded twisted pairs and an overall screen to cover all cores. The instrumentation cables should have individual screen(s), foil or braid over each twisted pair and an overall screen to cover all cores. Where permissible, and depending on the earthing scheme employed at the installation, the overall screen should be connected to the earthed metal work at both ends (360° bonding where possible). This may have multiple protective earth connections to the pipe work or the building structure and not connected to the individual screen(s) or Instrumentation or Zener barrier grounds. The individual inner screen(s) should be connected at one end only, normally the controller (e.g. Flow Computer) end. These should be connected to the Instrumentation or Zener barrier ground. Use suitable cables that meet BS5308 multi-pair Instrumentation Types 1 or 2

2. For each D-type connector, pass the connector hood over the cable and wire up the connector. Secure the hood and connector body together then connect the earth wire to the hood. Stick an identifying label on to the connector hood.

3. For each Klippon connector, wire up the connector then stick an identifying label on it.

4. Check the wiring thoroughly against the schedule and wiring diagram.

5. Attach all connectors to the Rear Panel.

Refer to Chapter 2 and Appendix C for examples of field transmitter connections and a full list of the 7951’spin identities.

4.9 Step 6: Earthing the instrument Caution: Incorrect earthing can cause many problems, so you must earth the chassis and the electronics correctly. The way in which you do this depends almost entirely on the type of installation you have and the conditions under which it operates. Therefore, because these instructions cannot cover every possible situation, the manufacturers recommend that earthing procedures should only be carried out by personnel who are skilled in such work.

The chassis of the 7951 must be earthed in all cases; both for safety reasons and to ensure that the installation complies with EMC regulations. Do this by connecting an earth lead from the stud on the rear panel (Figure 4.6) to a local safety earth such as a cabinet earth or some other suitable metal structure. If there is more than one 7951, see Figure 4.7 for correct and incorrect methods.

In addition to earthing the chassis, you may have to make extra earth connections in some cases, depending on the installation requirements. Details of internal earthing arrangements are in Appendix C.

Earthlead

Crinklewashers

Plainwashers

Nut

Thumbnut

Figure 4.6: The 7951’s Earth Stud


7951 (Ch04/DA) Page 4.7

7951 7951

79517951

2

7951 7951

79517951

OK

2

PL1

SK3

7951

1

(1) Earth stud on 7951 rear panel (D-type and Klippon).

(2) Cabinet earth or other suitable metal structure.

Figure 4.7: Multiple 7951 chassis earthing (through studs and earth leads)


Page 4.8 7951 (Ch04/DA)

4.10 Step 7: Connecting the power supply Plug the dc power connector into plug PL1 and switch on the power. The instrument goes through the following Power-On-Self-Test (POST) routine:

The display shows a sequence of characters or patterns to prove that all elements of the display are working. There is a pause of five seconds between each change of pattern.

The program ROM is checked against a checksum. The display shows how the test is proceeding.

Critical data are checked. The display shows the result of this check.

The coefficients are checked. The display shows the result of this check.

The battery-backed RAM is checked. The display indicates progress.

Any saved programs are checked. The display shows the number of programs and their status. Note that, for a new machine, there are no stored programs.

If a battery is fitted, its condition is checked and reported.

Note that, when the power is switched on, the alarms may light up. You can ignore these for the moment, as alarms are explained later in this manual. You can now proceed to configure your 7951 (see Chapters 7-11).

If the POST fails to complete, switch off the power supply and check all connections and the DIP-switch settings. Then re-connect the power supply. If the POST still fails to complete, switch off again and contact your supplier.

Chapter 5 The keyboard, display and indicators

7951 (Ch05/EA) Page 5.1

5. The keyboard, display and indicators

5.1 What this chapter tells you This chapter tells you: How the front panel is laid out. What the buttons and indicators do. What characters you can display.

5.2 The layout of the front panel Figure 5.1 shows the layout of the keyboard. The diagrams at the end of this chapter give a visual summary of what each of the buttons do.

1. DOWN-ARROW 7. ENTER 13. PRINT MENU

2. UP-ARROW 8. INFORMATION MENU 14. STREAM/RUN SELECT

3. MULTI-VIEW DISPLAY 9. LIMIT ALARM LED 15. F1 (software specific function)

4. LEFT-ARROW 10. INPUT ALARM LED 16. SECURITY LED AND LOCK

5. RIGHT-ARROW 11. SYSTEM ALARM LED

6. BACK 12. MAIN MENU

Figure 5.1: The layout of the front panel


Page 5.2 7951 (Ch05/EA)

5.3 What the display shows The display can show the following information: Numerical data in floating point, exponent or integer formats Text descriptors Units of measurement (if applicable) Status of parameters i.e. set, live, failed or fallback (if applicable) Alarm and event information Current time and date Identification number (location ID) of parameter Stream (metering-run) identification number (if applicable)

5.4 How the buttons work The buttons let you: Move around the menus. View data stored in the 7951 – VIEW mode. Edit the data – EDIT mode.

Some buttons do different things according to where you are in the menu system. For example:

ENTER button This button does nothing until you get into EDIT mode. After you have edited the data of a parameter, pressing ENTER accepts the changes and puts the 7951 back into VIEW mode.

c button When you move through the menu structure this selects any menu choice shown against the button. However, when in VIEW mode, pressing c lists the display units.

INFORMATIONMENU button

This button does nothing if you are in EDIT mode. At other times, it takes you to a special menu that provides information on alarms, events, flow status and 7951 operating mode.

PRINT MENU button

This button does nothing if you are in EDIT mode. At other times, it takes you to a special menu dealing with data archiving and printing of reports.

The sections that follow tell you more about what the buttons do and how you use them.

5.5 Using the buttons to move around the menus A general tour of the menu system is provided in chapter 6. The buttons, which you can use to move around the menu system, are:

UP-ARROW Moves the display up to the previous page of the menu. If there is no previous page, this button does nothing.

DOWN-ARROW Moves the display down to the next page of the menu. If there is no next page, this button does nothing.

:

a - d buttons Each of these buttons selects the menu choice next to it. If there is no menu choice next to a button, that button does nothing.

BACK Returns you to the previous step.


7951 (Ch05/EA) Page 5.3

MAIN MENU Moves you straight to page 1 of the top-level menu.

INFORMATIONMENU

Takes you to a special menu providing information on alarms, events, flow status and 7951 operating mode.

PRINT MENU Takes you to a special menu dealing with data archiving and printing of reports.

MULTI-VIEW You can define one or more display pages, each showing up to four items of data, lines of descriptive text, or both. Pressing MULTI-VIEW shows the first display page you have defined. Use the up/down arrow buttons to page up and page down.

F1 The use of this button is dependent on the functionality of the application software. If this button is in use, it will be mentioned in later chapters.

Note: All other buttons have no effect when moving around the menus.

5.6 Using the buttons to view stored data When a software parameter screen is viewed, after selection from the menu, the display is in VIEW mode.

Figure 5.2 shows a typical display when you view a software parameter screen. In VIEW mode, all information is in a right justified format.

Figure 5.2: A typical software parameter screen (in VIEW mode)

What the display shows

Line 1: Shows the parameter description. (Some words are abbreviated.)

Line 2: Shows the present value (or text for indirection type).

Line 3: Shows the measurement units (if any). This line is blank if there are no units.

Line 4: The right-hand side shows LIVE, SET, FB (FALLBACK) or FAIL to indicate the state of the present value shown in Line 2, where appropriate. These indications mean:

LIVE – The data shown is live data received from the transducer/transmitter connected to the 7951 or calculated by the 7858 rather than a set value.

SET – There is a fixed value for the data; this value does not change unless you enter a new fixed value or make it live.

FB – A fallback or default value has been used to obtain the value for the data.

FAIL – The live input has failed, most likely due to no transducer/transmitter being connected or a calculation failed to complete due to incorrect configuration.

An alarm will be raised causing the Input Alarm LED to flash on the front panel. For troubleshooting this alarm, see chapter 8.

Optionally, Line 4 may also show the parameter’s unique identification number (location ID), which is required when setting up certain features e.g. Multi-view. You can toggle this information on/off by the ‘a’ button.


Page 5.4 7951 (Ch05/EA)

In VIEW mode, the buttons that you can use are:

‘a’ button On/off toggle for displaying the parameter’s unique identification number (location ID). This is displayed to the left of the status indication on line 4.

‘b’ button Puts the 7951 into EDIT mode so that you can edit the data on line 2. The data being edited is left justified whilst in EDIT mode. (See next section)

‘c’ button Puts the 7951 into EDIT mode so that you can select from a list of the units in which the data can be displayed. The units are left justified whilst in EDIT mode. (See next section)

‘d’ button Puts the 7951 into EDIT mode so that you can select a status (Set or Live). The status is left justified whilst in EDIT mode. (See next section)

STREAM / RUN SELECT

If there is more than one stream (metering-run) and there is a number on the far left of display line 4, this button will select another stream (metering-run). The screen will be refreshed with attributes (value, units and status) for that stream (metering-run).

BACK Returns you to the previous step.

MAIN MENU Takes you straight to page 1 of the top-level menu.

5.7 Using the buttons to edit information You can: Edit text Select an option from a multiple-choice list Edit numerical information Edit the date and time

5.7.1 Text editing Once in EDIT mode (see earlier), the buttons that you use to edit text are:

LEFT-ARROW Moves the cursor to the left, along the line of text you are editing.

RIGHT-ARROW Moves the cursor to the right, along the line of text you are editing.

UP-ARROW This button changes the character at the current cursor position. It scrolls forwards through the alphanumeric character set. Stop when the character you want is displayed.

DOWN-ARROW Changes the character at the current cursor position. It scrolls backwards through the alphanumeric character set. Stop when the character you want is displayed.

:

0 - 9 buttons Each button enters a single digit.

‘b’ button If you are satisfied with the changes you have made, press b to accept the changes and go back to VIEW mode. (The ENTER button also does this.)


7951 (Ch05/EA) Page 5.5

ENTER If you are satisfied with the changes you have made, press ENTER to accept the changes and go back to VIEW mode. (The ‘b’ also does this.)

CLEAR This clears a line of text.

BACK If you do not want to keep the changes you have made, press the BACKbutton to abandon the changes and go back to VIEW mode.

PLUS / MINUS Toggles between lower and upper case letters.

5.7.2 Multiple-choice option selection Once in EDIT mode (see earlier), the keys that you use to select from a multiple-choice list are:

UP-ARROW Scrolls up through the available options.

DOWN-ARROW Scrolls down through the available options.

‘b’ button If editing the data (on display line 2) and you are satisfied with the change you have made, press the ‘b’ to accept the change and go back to VIEW mode. (Note: The ENTER button also does this.)

‘c’ button If editing the measurement unit selection and you are satisfied with the change you have made, press the ‘c’ to accept the change and go back to VIEW mode. (Note: The ENTER button also does this.)

‘d’ button If editing the status selection and you are satisfied with the change you have made, press the ‘d’ to accept the change and go back to VIEW mode. (Note: The ENTER button also does this.)

ENTER If you are satisfied with the change you have made, press the ENTERbutton to accept the change and go back to VIEW mode.

CLEAR Restore the previous contents.

BACK If you do not want to keep the changes you have made, press the BACK button to abandon the changes and go back to VIEW mode.

5.7.3 Numerical editing Once in EDIT mode (see earlier), the buttons that you use to edit numerical data are:

LEFT-ARROW Erases the digit to the left of the cursor.

:


PLUS / MINUS This changes the sign of the number. Pressing it will toggle between PLUS and MINUS signs.

DOT Inserts a decimal point.


Page 5.6 7951 (Ch05/EA)

EXPONENT Use this button if you want to show numbers in exponent form.

‘b’ button If you want to accept the changes you have made, press the ‘b’. The 7951 will then revert to VIEW mode. (Note: ENTER also does this.)

ENTER If you want to accept the changes you have made, press the ENTER key. The 7951 will then revert to VIEW mode. (Note: ‘b’ also does this.)

CLEAR Clears the line you are currently editing.

BACK If you do not want to keep the changes you have made, press the BACKbutton to abandon the changes and go back to VIEW mode.

Numerical entry When you type in a number the first digit appears at the left of the display and each successive digit is then positioned to the right of the one just entered. A number being entered over-types any existing number.

Parameter identification number (Location ID) entry These appear on the display in the same way as for numerical entry. However, when you accept the number (by pressing ‘b’ or ENTER), the text descriptor of the parameter with that particular number appears on line 2. You will encounter this type of ‘pointer’ (indirection) editing if configuring the Multi-view display (see chapter 11).

5.7.4 Date and time editing

The date and time are displayed in the format: dd-mm-yyyy hh:mm:ss. When you edit the date and time, the cursor moves to the right but skips the ‘:’ and ‘-’ characters.

LEFT-ARROW Moves the cursor to the left.

RIGHT-ARROW Moves the cursor to the right.

:


‘b’ button If you want to accept the changes you have made, press ‘b’. The 7951 will then revert to VIEW mode. (Note: ENTER also does this.)

ENTER If you want to accept the changes you have made, press ENTER.The 7951 will then revert to VIEW mode. (Note: ‘b’ also does this.)

CLEAR Restore the previous contents.

BACK If you do not want to keep the changes you have made, press the BACK button to abandon the changes and go back to VIEW mode.

The new date and time is validated. An invalid date and time is causes the message “Bad date/time” to appear on-screen for a few seconds before the previous content is restored.


7951 (Ch05/EA) Page 5.7

5.8 The 7951 character set You can use any of the 96 characters shown below as part of your display.

Figure 5.3: The 7951 character set

5.9 LED indicators

Security Indicator This LED shows the present security level of the system. RED FLASHING – The instrument is at Calibration level. RED – Engineer level: the instrument can be configured. ORANGE – Operator level: limits can be changed. GREEN – World level: no parameters can be changed.

Note: For more information about these, see Chapter 11.

1. Security Level LED.

Figure 5.4: Alarm Indicators

Alarm Indicators These are the Input, System and Limit alarms. For more information about these, refer to Chapter 8: “Alarms and Events”.

1. System alarm LED. 2. Input alarm LED. 3. Limit alarm LED.

Figure 5.5: Alarm Indicators


Page 5.8 7951 (Ch05/EA)

5.10 Summary of button functions The tables here provide a visual summary of the function for each button when in various modes.

Table 5.1: Summary of what the buttons do (Part 1 of 2)


7951 (Ch05/EA) Page 5.9

Table 5.2: Summary of what the buttons do (Part 2 of 2)


Page 5.10 7951 (Ch05/EA)

Chapter 6 The menu system

7951 (Ch06/GA) Page 6.1

6. The menu system

6.1 What this chapter tells you Before you can configure and operate the 7951, you should have some understanding of how the menu system works. The menus are simple and intuitive, so they should present no problems to the average user.

This chapter gives you a general tour, showing how to navigate the menu system to find application parameter screens and other types of screen such as for entering passwords.

Note:The menus will differ between software versions, and can differ between releases of a software version.

Chapter 12 features tables showing the routinely used (operator) parts of the menu system used in your software.

6.2 What the menu system does The menu system lets you:

Configure the 7951. Operate it. View data and settings stored in the 7951. Edit data stored in the 7951.

6.3 How the menu system works When you power-on the 7951, the menu system appears immediately after the routine Power-On-Self-Test (POST) is completed. If it is the first power-on since the software was installed, a screen appears showing the software version number and the issue number. if this is not the case, the screen will be the last visited menu location prior to powering off (or a power failure).

Press the MAIN MENU button once and page 1 of the top-level menu will appear (see Figure 6.1).

The menu system is a tree-like structure that repeatedly branches to lower levels until a final screen is reached. Page 1 of a top-level menu shown in Figure 6.1. It comprises four menu choices – Flow rates, Flow totals, Density and Viscosity.

Each menu choice has a description e.g. “Flow rates” and a triangular icon e.g. alongside to indicate the type of menu choice. A non-filled, triangular icon ( ) indicates the menu choice leads to a lower-level menu (sub-menu). A filled, triangular icon ( ) indicates the menu choice leads to a non-menu screen.

Note: The menus may be different in your software.

Figure 6.1: page 1 of a top-level menu


Page 6.2 7951 (Ch06/GA)

Each menu choice is associated by position with a lettered button on the front panel - a, b, c or d. For example, a menu choice on Display Line 1 is associated with the a button. Similarly, a menu choice on Display Line 2 is associated with the b button, and so on. If there is no menu choice on a display line, the associated letter button will not do anything.

When you do make a menu choice from a menu using the lettered buttons, the display changes to show the selected lower-level menu or a non-menu screen.

Figure 6.2 shows an example where pressing the a button will lead to a lower-level menu for “Flow rates”. Similarly, the b button leads to a lower-level menu for “Flow totals”.

Using the BACK button will return you to the previous menu level, which, in this example, is the top-level menu shown in the middle.


Figure 6.2: Menu Choice Selection

Where a menu has more choices than can fit on to the 4-line display, the menu comprises of two or more pages. Vertical arrow icons appear on the left-hand side of display to indicate there are further pages on the same menu level. Figure 6.3 shows how you can scroll up or down between the pages by using the UP-ARROW and DOWN-ARROW buttons. These buttons will do nothing if there is no page to scroll to.


Figure 6.3: Pages of a Main Menu


7951 (Ch06/GA) Page 6.3

At the lowest levels in each branch of the menu system, there are parameter screens. Figure 6.4 shows how to navigate to the parameter screen for <MeterRun Temperature>. All parameter screens feature a solid, black, triangular shaped mark in the bottom-left corner of Display Line 4.

Note: Full details about editing parameters can be found in Chapter 5.


Figure 6.4: A typical software parameter screen

Returning to the top-level menu again, there are menu choices that are common to all software versions (Figure 6.5). In addition, you’ll encounter them in subsequent chapters.

All other menu choices on the Main Menu (e.g. “Flow rates”) are for operators to quickly find final measurements and other calculation results. Chapter 12 has tables showing these menus in more detail.

Figure 6.5: Menus common to all software versions

Leads to a screen for entering a password to change security level. (See Chapter 11).

Leads to menus for viewing interim results of measurements and other

calculations, Inputs, Outputs, etc. (See Chapter 12 for a full map)

Leads to menus for editingmeasurement tasks for your installation. (See Chapters 7 - 11).


Page 6.4 7951 (Ch06/GA)

Chapter 7 Serial Communications and Networking

7951 2510 (Ch07/FC) Page 7.1

7. Serial Communications and Networking

7.1 What this chapter tells you This chapter is a comprehensive guide to serial RS-232/485 port communications with the 7951. Since this subject area is vast, with countless reference books, the scope is restricted to the 7951 point-of-view. Therefore, it has been assumed that the reader has a reasonable working knowledge of data communications and networking.

A highly recommended reference for this chapter is: The 1992 edition of “MODICON MODBUS PROTOCOL REFERENCE GUIDE (PL_MBUS-300)”.

Note: This chapter is not a guide to the MODBUS protocol

7.2 7951 Communication Capabilities The 7951 has extensive facilities – ports and data services – to allow the communication of data with almost any device that has support for the Modicon MODBUS protocol.

Communication ports and their associated standards are summarised in Table 7.1. Various data services are available through the ports and are introduced in Section 7.2.2.

Table 7.1: 7951 Communications Ports and Supported Standards

Serial Port One

Serial Port Two

Serial Port Three

RS-232C RS-232C/485 RS-232C/485 MODBUS MODBUS MODBUS

7.2.1 Communication Ports

Serial RS-232/485 Ports Two serial interface standards are supported by the 7951 – Serial RS-232C (full duplex) and Serial RS-485(half duplex). They are software selectable if there is a choice for a particular port.

RS-232C is the usual choice for a direct (point-to-point) network connection with only one device. Typically, it is utilised when transmitting printed reports to an ASCII compatible output device, such as a printer or a terminal. Another main use is the ‘Peer-to-Peer List’ data service that can regularly broadcast parameter values to another 7951 instrument. Data services are introduced in Section 7.2.2.

RS-485 is the choice when establishing a multi-drop network with two or more devices. This network allows both Master/Slave and Peer/Peer arrangements of devices and, subsequently, full availability of all data services. Data services are introduced in Section 7.2.2.

7.2.2 Data Services

Table 7.2 lists the data services that are available through any serial RS232/485 port.

Services are accessed by a half-duplex exchange of MODBUS – request and response - messages between the 7951 instrument and another MODBUS device. Guided examples with the necessary message sequences to correctly access services are given later in Chapter 7 and in any extra pages that are inserted between Chapters 7 and 8.


Page 7.2 7951 2510 (Ch07/FC)

Table 7.2: Data Services Availability (Master/Slave)

Data Services Available on Master/Slave Purpose of Data Service

Database Access Slave Allow any (non-7951) MODBUS Master device to perform read/writes on an individual parameter in the database of a Slave

Historical Alarm Log Slave Retrieval of LIVE alarm information from the Historical Alarm Log. (Events are explained in Chapter 8 of this manual)

Historical Event Log Slave Retrieval of LIVE event information from the Historical Event Log. (Alarms are explained in Chapter 8 of this manual)

High Speed List 1 * Slave Allow non-7951 MODBUS Master device to perform fast read/writes on an arranged group of up to 150 parameters.

High Speed List 2 * Slave Allow non-7951 MODBUS Master device to perform fast read/writes on an arranged group of up to 150 parameters.

Archive Access Slave Retrieval of software parameter data from any of the data archives. (Archiving is explained in Chapter 9 of this manual)

Peer-to-Peer * Master Allow 7951 MODBUS Master to perform read/writes on software parameters in the database of multiple 7951 MOBUS slaves

* This application data service is fully explained in the extra pages between Chapter 7 and Chapter 8


7951 2510 (Ch07/FC) Page 7.3

7.3 MODBUS from the 7951 view-point 7.3.1 Introduction

The Modicon MODBUS specification is designed to transfer data in 1-bit (coil) or 16-bit (register) blocks. This protocol has not been designed to deal with data, such as floating-point numbers, which require a minimum of 32-bit blocks. For this reason, every manufacturer of computer equipment that deals with this type of data must decide in which way the protocol should be extended. Consequently, many different implementations exist for the transfer of 32-bit floating-point data.

7.3.2 Supported Commands

The 7951 supports three MODBUS functions: 1. Function 03 – Read multiple registers 2. Function 06 – Write single register 3. Function 16 – Write multiple registers

Data stored within a 7951 is represented by one or more 16-bit registers. Where registers contain a collection of bits, the 16-bit register is still used rather than individual bit (coil) access.

The 7951 supports both single and multiple register access. Each port is configured individually to allow one type of register access.

Multiple Register Access: ‘write’ command involving a 21-byte character string will specify 11 registers.

Single Register Access: ‘write’ command involving the same character string will specify just 1 register.

7.3.3 Floating Point Numbers

Floating-point values within the software parameter database are stored as 64-bit IEEE (double-precision) numbers. When requested over a MODBUS network link, a floating-point value is either encoded as a 32-bitIEEE (single-precision) number or encoded as a 64-bit IEEE (double-precision) number.

The precision level is individually selectable for each communication port.

7.3.4 Word Swap Mode

Since Modicon did not define 32-bit data transfers, the order of transmission for (2 x 16-bit) words of a 32-bit value is also not defined. The 7951 therefore provides the facility to choose whether the first or second word is the most significant. For 64-bit numbers, word swap places the second double-word as the most significant.

This mode is individually selectable for each port.

Figure 7.3.1: Word Ordering Examples

WORD '1'(16 Bits)

WORD '2'(16 Bits)Default Order

Word Swap

42 C2 3F 0D

WORD '1'(16 Bits)

WORD '2'(16 Bits)

42 C23F 0D

SINGLE PRECISION

WORD '1'(16 Bits)


Word Swap

40 58 47 E1

WORD '3'(16 Bits)

WORD '4'(16 Bits)

9B 90EA 9E

DOUBLE PRECISION

WORD '3'(16 Bits)

WORD '4'(16 Bits)

9B 90 EA 9E

WORD '2'(16 Bits)

WORD '1'(16 Bits)

47 E1 40 58


Page 7.4 7951 2510 (Ch07/FC)

7.3.5 MODBUS Addressing Unlike most MODBUS devices, the 7951 can respond to more than one MODBUS address through a communication port.

The base address of a MODBUS Slave is programmable and is used for accessing the database of software parameters. It is also possible to configure a 7951 to allow access to further data services through virtual addressing – consecutive MODBUS addresses offset beyond the base address.

You do not need to edit these virtual addresses because they are at fixed offsets beyond the programmed base address. The offsets are illustrated in Table 7.3. A virtual address becomes active when the corresponding data service is enabled.

Note: There can be different base addresses programmed for each individual port if you require it. However, the fixed address offsets still apply and will access exactly the same data service.

Table 7.3: Data Services and MODBUS Addressing

MODBUS Addressing Data Service Address Offset

Base address Software Parameter Database +0 (Base address) Peer-to-Peer Lists (+0)

Virtual Address ‘1’ Historical Alarm & Event Log +1 Virtual Address ‘2’ High Speed List ‘1 +2 Virtual Address ‘3’ High Speed List ‘2’ +3 Virtual Address ‘4’ Data Archives +4 Note: ‘Peer-to-Peer List’ functions also use the ‘Software Parameter Database’

service of a 7951 MODBUS Slave


7951 2510 (Ch07/FC) Page 7.5

7.4 Connecting the 7951 to a RS-232/RS-485 Link This section is a reference with a table of grouped rear panel pins for each serial port and each physical layer interface.

7.4.1 RS-232 (full duplex) Rear Panel Pin Connections

RS-232C Serial Interface Pin Groups (Port ‘1’)

7951 Function

Com 1 Tx SK1/2 Transmit data Com 1 Rx SK1/3 Receive data Com 0V SK1/5 0V GND (Signal Ground)


7951 Function

Com 2 Tx Sk2/2 Transmit data Com 2 Rx Sk2/3 Receive data Com 0V Sk2/5 0V GND (Signal Ground)

Com 2 CTS Sk2/7 Clear to send Com 2 RTS Sk2/8 Request to send


7951 Function

Com 3 Tx SK3/2 Transmit data Com 3 Rx SK3/3 Receive data Com 0V SK3/5 0V GND (Signal Ground)

Com 3 CTS SK3/7 Clear to send Com 3 RTS SK3/8 Request to send

A simple MODBUS network can consist of just two devices. They could be a PC and a 7951 connected by a RS-232C ‘straight through’ cable:

7951

Tx

Rx

Rx

Signal Ground

Tx2

5

3

SK2/2

SK2/3

SK2/5

PC D-type Com port

RTS

CTS7

8

SK2/7

SK2/8

7951

Tx

Rx

Rx

Signal Ground

Tx2

5

3

SK1/2

SK1/3

SK1/5

PC D-type Com port


Page 7.6 7951 2510 (Ch07/FC)

7.4.2 RS-485 (half duplex) Rear Panel Connections

This section is a reference with a table of grouped rear panel pins for each serial port and the RS-485 signalling standard.

RS-485 Serial Interface Pin Group (Port ‘1’) Note: There is no support for RS-485 on port one.

RS-485 Serial Interface Pin Group (Port ‘2’) 7951 Function

Com 2 Rx/Tx+ SK2/1 Transmit/receive data + Com 2 Rx/Tx- SK2/9 Transmit/receive data -

Com 0V SK2/5 0V GND (Signal Ground)

RS-485 Serial Interface Pin Group (Port ‘3’) 7951 Function

Com 3 Rx/Tx+ SK3/1 Transmit/receive data + Com 3 Rx/Tx- SK3/9 Transmit/receive data -

Com 0V SK3/5 0V GND (Signal Ground)

Stream 2Stream 1Prover

Tx/Rx-

Tx/Rx+

Signal Ground

7951

SK3/1

SK3/9

SK3/5

7951 7951

SK3/1

SK3/9

SK3/5

Tx/Rx-

Tx/Rx+

Signal Ground

SK3/1

SK3/9

SK3/5


7951 2510 (Ch07/FC) Page 7.7

7.5 After Connecting the 7951… This section explains how to proceed with configuring the communication parameters of the 7951 after all the wiring to external communication devices is completed, as guided in Section 7.4.

RS-232: Complete Section 7.5.1 and then complete Section 7.5.2 RS-485: Complete Section 7.5.1 and then complete Section 7.5.3

7.5.1 General RS-232C/485 Port Configuration

This Section is for configuring basic communication parameters before moving on to the RS-232C and RS-485 configuration sections.

Objective:Set-up the parameters for each serial port with an RS-232 (point-to-point), or RS-485 (multiple-drop) network connection.

What to do here:Follow these instructions for each port:

1. Navigate to this menu: <“Configure”>/<”Other parameters”>/<“Communications”>/<“Ports”>

2. Select the sub-menu for a serial port.

3. Work through this menu data checklist: (Note: Some localised menu searching is required)

Parameter Instructions and Comments

Port Baud rates Select a transmission rate that is compatible with other networked device(s) Port Char Format Select a character format that is compatible with for other networked device(s) Port handshaking Select the option descriptor of either “None”, “Xon/Xoff” or “CTS/RTS” Port RS232 / 485 Select the serial interface standard for the network. Also, read Note B

Notes: A On-screen parameter names incorporate a number to identify the associated serial port. B Not all 7951 communication ports have support RS-485. For further information, see page 7.1.

4. Repeat all previous steps for each RS-232/485 port that you intend to use.

(End of instructions)

7.5.2 RS-232 Configuration This section is for completing the configuring of software parameters for a point-to-point communication link with another RS-232C device.

Objective:Set-up the parameters for serial ports with an RS-232C connection.

What to do here:Follow these instructions: 1. Navigate to this menu: <“Configure”>/<”Other parameters”>/<“Communications”>/<“Ports”>

2. Select the sub-menu for a serial port with the RS-232C connection

3. Locate the menu data page with a descriptor of “Comms port owner” (or similar)

4. Select an option descriptor Select the option with “Printer” when the RS-232C device is an ASCII compatible output device, such as a printer. Otherwise, select either “Master” or “Slave”, depending on which data services are needed.

5. Test the RS-232C connection, perhaps by printing a report



Page 7.8 7951 2510 (Ch07/FC)

7.5.3 RS-485 Configuration

This section is for completing the configuring of software parameters for serial ports with an RS-485 communication link into a multi-drop (MODBUS Master/Slave) network.

Objective:Set-up the 7951 to function as a MODBUS Slave. This will allow for ‘remote’ accessing of various application data services by a MODBUS Master.

What to do:

Follow these instructions:

1. Ensure that general port parameters have already been configured, as guided in Section 7.5.1.

2. Navigate to this menu: <“Configure”>/<”Other parameters”>/<“Communications”>/<“Ports”>

3. Select the sub-menu for a RS-485 port.

4. Work through the checklist of Error! Reference source not found..


Table 7.4: RS-485 Software Parameters

Parameters Instructions and Comments Notes?

Comms port owner Select the option descriptor with “MODBUS Slave” APort MODBUS mode Select the transmission mode (as agreed for the Master) A

MODBUS word order Selection is dependent on configuration of the Master A, C

MODB slave add ‘Set’ a value for the MODBUS base address of the port (slave) A, C, D

P MODBUS Features Select data services that are accessible by a Master (through this port) A, B

Long reg access Selection is dependent on configuration of the Master A, C

MODB precision Selection is dependent on configuration of the Master A, C

Notes: A On-screen parameter names incorporate a number to identify the associated serial RS-485 port B Table 7.5 shows how the multiple-choice option descriptors relate to enabling access to one or more data

services through a port.C See page 7.3 for guidance. D The 7951 Flow Computer can be MODBUS Slaves at different base addresses on each port. It is possible to

have an identical base address on two or more ports when they are not connected to the same network.

Table 7.5: Virtual Slave Access - Enabling Codes

Option Descriptors A&E HSL ‘1’

HSL ‘2’ DA

None

Alarm

Alarm + List1

Alarm+List1+List2

Alarm+L1+L2+L3

Alarm+L1+L2+L3+L4 Alarm + L1+L2+L3+L4+DL

Key: = Enabled, A&E = Virtual Slave ‘1’, HSL = High Speed List Slave, DA = Data Archive Slave


7951 2510 (Ch07/FC) Page 7.9

7.6 7951 Database access over a MODBUS network This section demonstrates how a (non-7951) MODBUS Master can communicate with the software parameter database of a 7951 MODBUS Slave.

7.6.1 Introduction There are several types of information that can be obtained from the software parameter database:

1. Parameter value (in base units of measurement) 2. Parameter value status. 3. Data size and data type attributes for a software parameter value.

The 7951 uses a unique index called a location identification (ID) number. There is a unique ID number for every stored software parameter. The location ID number is not normally displayed, but pressing the abutton when a parameter page is displayed, will display the number on the fourth line.

MODBUS registers are expressed as the location ID number minus 1. Therefore, a requesting device will ask for MODBUS register 16 in order to read the data of the software parameter with an ID of 17.

NoticeParameter attributes and location identification (ID) numbers of the database with your installed software is likely to be different to those used in these examples. For a full list of parameters, locate the ASCII text file with the filename extension ‘.MAN’ on your ‘FC CONFIG’ installation media.

A number of worked examples are provided for each information type. Every example features objectives, actions, and results. Adapt the examples to suit your requirements.

Objective For an example, the objective could be to read a value from a specific parameter.

Action(s) This consists of one or more ‘read’ and ‘write’ MODBUS protocol commands (framed messages), shown as a sequence of hexadecimal values. The framed messages need to be transmitted by the MODBUS Master. Responses are also shown as a sequence of hexadecimal values.

Table 7.7 contains a list of all the abbreviations of meanings that can appear with a sequence. Use them to distinguish the important elements of the sequence.

Result This is a brief analysis of the MODBUS response to an action. There may be a reference to additional information. Some software parameters may have a “No access” security attribute and, therefore, be permanently unavailable. The response from a command to read such data is shown in Table 7.6.

Table 7.6: "No Access" to Data Response

Receive 0A 83 …

Meaning Slv. Err. …


Page 7.10 7951 2510 (Ch07/FC)

Table 7.7: Abbreviations for Interpreting Elements of Transmit and Receive Sequences

Abbreviations Meaning

Slv. The MODBUS slave base address Err. Error code. E.g. 83 = Error reading / Exception Fn. MODBUS Function code. E.g. 03 = Read multiple registers

Reg. Cnt Number of registers to read or write / Number of registers read or written Reg. ID MODBUS Register number

DC Data Count – The number of bytes of data that follow The Data Data bytes that contain the useful information Chk sum Calculated checksum - always two bytes at the end


7951 2510 (Ch07/FC) Page 7.11

7.6.2 7951 Database Information: Software Parameter Values

Software parameter values are mapped within the first 10,000 registers of the MODBUS register map directly associated with the programmed base address of a 7951 MODBUS slave. Our examples assume the MODBUS Slave (port) is configured with a base address of “01”.

Notes: Identification (ID) numbers of the software parameters with your installed software may be

different to those used in these examples. All request and response messages shown here use (1) the ‘default word order’ mode, (2) 32-bit single

precision encoding and (3) multiple read/write register MODBUS functions.

Example 1: Read base density value from database location 0787

MODBUS Action: Read from MODBUS register 0786

Transmit 01 03 03 12 00 02 64 4A Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 01 03 04 44 54 A0 00 D7 13 Meaning Slv. Fn. DC The Data Chk. Sum

Result: The data value part of the reply, 0x4454A000, translates from a 32-bit IEEE number into the floating-point number 850.50 (in Kg/m3 – base units).

Example 2: Write base density value of 850 Kg/m3 (base units) to location 0787

MODBUS Action: Write to MODBUS register number 0786

Transmit 01 10 03 12 00 02 04 44 54 80 00 53 6A Meaning Slv. Fn. Reg. ID Reg. Cnt DC IEEE 32-bit data value Chk. Sum

Receive 01 10 03 12 00 02 E1 89 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Result:Base density value changes. The 0x44548000, translates from a 32-bit IEEE number into the floating- point number 850.00 (in Kg/m3 – base units).

Example 3: Check on selected option descriptor of a multiple-choice list

Objective: Check referral method selection for calculating Metering density.

MODBUS Action: Read from MODBUS register 03661 (0x0E4D)

Transmit 01 03 0E 4D 00 01 16 F5 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 01 03 02 00 00 B8 44 Meaning Slv. Fn. DC The Data Chk. Sum

Result: The returned data value 0x0000 can be interpreted by looking at the following table:

Value Meaning

0x0000 4x5 Matrix Referral selected

0x0001 API Referral selected


Page 7.12 7951 2510 (Ch07/FC)

7.6.3 7951 Database Information: Software Parameter Status

Software parameter states are mapped within registers 30001 to 40000 of the MODBUS register map directly associated with the programmed base address of a 7951 MODBUS slave. Our examples assume the 7951 MODBUS Slave (port) is configured with a base address of “01”.




Example 1: Read the status of location 0787

MODBUS Action: Read MODBUS register 30786 (30000 offset + 0787 - 1)

Transmit 01 03 78 42 00 01 3C BE Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 01 03 02 00 01 79 84 Meaning Slv. Fn. DC The Data Chk. sum

Result: The “00 01” indicates a ‘SET’ status. Refer to Table 7.9 (on page 7.12) for other states.

Example 2: Change the status of location 0787

MODBUS Action: Change status to ‘LIVE’ by writing to 0x0000 to register 30786 (30000 + 0787 - 1)

Transmit 01 10 78 42 00 01 02 00 00 51 75 Meaning Slv. Fn. Reg. ID Reg. Cnt. DC The Data Chk. sum

Receive 01 10 78 42 00 01 B9 7D Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Result: Status has changed to “Live”. (See Table 7.8 on page 7.12 for other states)

Table 7.8: Status Codes (Selection)

Value Selection

0x0000 Live state 0x0001 Set state

Table 7.9: Status Codes (Returned)

Value State Return

0x0000 Live 0x0001 Set 0x0002 Fail 0x0003 Fallback 0x00FF No state


7951 2510 (Ch07/FC) Page 7.13

7.6.4 7951 Database Information: Size and Type of Software Parameter Value

The data size and type of every software parameter value is mapped within registers 20,001 to 29,999 of the MODBUS register map directly associated with the programmed base address of a 7951 MODBUS slave. Our examples assume the 7951 MODBUS Slave (port) is configured with a base address of “01”.




Example 1: Read size and type of data available from location 0787

MODBUS Action:Read MODBUS register 20786 (20000 offset + 0787 - 1)

Transmit 01 03 51 32 00 01 35 39 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 01 03 02 07 04 BB B7 Meaning Slv. Fn. DC The Data Chk. Sum

Result:2 bytes of data are returned in the reply: 0x07 and 0x04 * 0x07 = Data Type Code 7 – a 32-bit floating-point number * 0x04 = 4 bytes needed to represent the floating-point value

Special Note: For other data type and size codes, refer to Table 7.10 on page 7.14

Example 2: Read size and type of data available from location 1579

MODBUS Action: Read MODBUS register 21,578 (20000 offset + 1579 - 1)

Transmit 01 03 54 4A 00 01 B5 EC Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 01 03 02 09 16 3F DA Meaning Slv. Fn. DC The Data Chk. Sum

Result:2 bytes of data are returned in the reply: 0x09 and 0x16 * 0x09 = Data Type Code 9 – Character String* 0x16 = 22 bytes – length of character string in bytes


Page 7.14 7951 2510 (Ch07/FC)

Table 7.10: Interpreting Responses from Type 3 Requests

Type of Data Size (Bytes) Type (Code)

Character 2 1 Unsigned 8-bit integer 2 2 Unsigned 16-bit integer 2 3 Signed 16-bit integer 2 4 Unsigned 32-bit integer 4 5 Signed 32-bit integer 4 6 32-bit floating point number 4 7 64-bit floating point number 8 8 Character String 22 9 Multiple-choice (List) Option 2 10 Location pointer 2 11 Time and date 16 12

Table 7.11: Unit of Measurement Category Codes

Category Code Unit Category Category

Code Unit Category

0 (No units) 20 (Not Used) 1 Temperature 21 (Not Used) 2 Pressure 22 (Not Used) 3 Differential Pressure 23 Time 4 Volume 24 Length 5 Standard Volume 25 Speed 6 Mass 26 Fraction 7 Energy 27 Saybolt Universal 8 Density 28 Saybolt Temperature 9 Standard Density 29 Absolute Zero 10 Frequency 30 Temperature Offset 11 Period 31 General 12 Dynamic Viscosity 32 (Not Used) 13 Base Dynamic Viscosity 33 (Not Used) 14 Kinematic Viscosity 34 (Not Used) 15 Base Kinematic Viscosity 35 Expansion Coefficient 16 Flow Factor 36 Youngs Modulus 17 Volume Rate 37 Velocity 18 Standard Volume Rate 19 Mass Rate


7951 2510 (Ch07/FC) Page 7.15

7.6.5 7951 Database Information: Full Attributes of a Software Parameter

The data size and type of every software parameter value is mapped within registers 40,001 to 49,999 of the MODBUS register map directly associated with the programmed base address of a 7951 MODBUS slave. Our examples assume the 7951 MODBUS Slave (port) is configured with a base address of “01”.




Example 1: Read the full attributes of location 0787

MODBUS Action:Read MODBUS register 40786 (40000 offset + 0787 - 1)

Transmit 01 03 9F 52 00 02 4B CE Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 01 03 04 04 07 01 08 BA D0 Meaning Slv. Fn. DC The Data Chk. Sum

Result:4 bytes of data are returned in the reply: * 0x04 = 4 bytes – required to store a 32-bit floating-point number * 0x07 = Data Type Code 7 – software parameter value is a 32-bit floating-point number* 0x01 = Status Code 1 – “Live” value state * 0x08 = Unit of Measurement Category Code 9 – Density units

Special Note: For interpreting other codes, refer to Table 7.10 (on page 7.14) and Table 7.11 (on page 7.14) The reply data is unaffected by the ‘word order’ mode


Page 7.16 7951 2510 (Ch07/FC)

7.7 Historical Alarm Log access over a MODBUS Network This section demonstrates how a MODBUS Master can access “LIVE” information from the Historical Alarm Log of a 7951 MODBUS Slave.

Refer to Chapter 8 if an explanation for the Historical Alarm Log is required.

7.7.1 Introduction

Information from the Historical Alarm Log is available to a MODBUS Master through the register map of Virtual Address ‘1’ (base address + offset of 1).

Warning! It is not advisable to clear or accept alarms using the front panel while the Historical Alarm Log is being queried by a MODBUS master. Doing so could result in the MODBUS Master having an incorrect view of the content.

Worked examples are provided to demonstrate the correct method for (1) obtaining details of an alarm, (2) accepting that alarm, and (3) clearing that alarm.

Every example features objectives, request/response sequences, and an explained result. Adapt the examples to suit your requirements.




Result This is a brief analysis of the MODBUS Slave response to an action. There may be a reference to additional information.







7951 2510 (Ch07/FC) Page 7.17

7.7.2 Worked Examples

Unless otherwise stated, all request and response messages shown here use (1) the ‘default word order’ mode, (2) 32-bit single precision encoding and (3) multiple read/write register MODBUS functions.

A base address of “01” has been assumed for or examples.

7.7.2.1 Example 1 (of 3) Objectives: 1. Find out how many alarms are in the Historical Alarm Log. 2. Retrieve identification numbers for logged alarms. 3. Make information on a specific alarm available. 4. Get further information about the alarm that was selected in step three. 5. Accept the alarm that was selected in step three. 6. Clear the alarm that was selected in step three.

Step 1 is to find out how many alarms are in the Historical Alarm Log.

MODBUS Action 1 of 1: Count alarms by reading MODBUS register 1,999

Transmit 02 03 07 CF 00 01 B5 72 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 02 03 02 00 10 FD 88 Meaning Slv. Fn. D.C. The Data Chk. Sum

Result: Reply data indicates that there are 16 (0x0010) alarms in the Historical Alarm Log.

Step 2 is to retrieve the identification number of the second oldest alarm

MODBUS Action 1 of 1: Read MODBUS register 1

Transmit 02 03 00 01 00 01 D5 F9 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 02 03 02 00 17 BC 4A Meaning Slv. Fn. DC The Data Chk. Sum

Result: Reply data indicates that the unique alarm ID is 0x0017

Note:Identification numbers of presently logged alarms are held in MODBUS registers 0 to 29 of the map for virtual address ‘1’. The first entry in the Alarm Historical Log is always at MODBUS register 1. For the purpose of this worked example, one alarm identification number is sufficient.

Step 3 is to make information on an alarm available. This is mandatory for remaining steps.

MODBUS Action 1 of 2: Make information available on the second alarm Write alarm ID number, 0x0017, to MODBUS register 999

Transmit 02 10 03 E7 00 01 02 00 17 D6 79 Meaning Slv. Fn. Reg. ID Reg. Cnt. DC The Data Chk. Sum

Receive 02 10 03 E7 00 01 B1 89 Meaning Slv. Fn. Reg.ID Reg. Cnt. Chk. Sum

Result: Reply data indicates that the selection has been made


Page 7.18 7951 2510 (Ch07/FC)

MODBUS Action 2 of 2:

Check that information is now available by reading MODBUS register 999

Transmit 02 03 03 E7 00 01 34 4A Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 02 03 02 00 17 BC 4A Meaning Slv. Fn. DC The Data Chk. Sum

Result: Reply data indicates that the current alarm ID is confirmed to be 0x0017.

Note: reply of 0x0000 indicates that no alarm has been selected

Step 4 is to get further information about the alarm that was selected in step three. To get information about another alarm, repeat step three but use another identification number.

MODBUS Action 1 of 1: Obtain alarm text length by reading MODBUS register 2000

Transmit 02 03 07 D0 00 01 84 B4 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 03 03 02 00 12 84 B4 Meaning Slv. Fn. DC The Data Chk. Sum

Result: Reply data indicates that the alarm text length is 18 bytes (0x0012). At present, the length returned is always 18 bytes. Divide the length by 2 to work out the number of register to request when asking for the text. Do not assume the length will always be 18 bytes.

MODBUS Action 1 of 1: Obtain ASCII alarm text by reading MODBUS register 1011

Transmit 02 03 03 F3 00 09 75 88 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 02 03 12 53 69 6D 65 70 65 72 69 6F 64 20 Meaning Slv. Fn. DC ‘T’ ‘i’ ‘m’ ‘e’ ‘p’ ‘e’ ‘r’ ‘i’ ‘o’ ‘d’

Receive 6E 6F 20 63 61 6C 00 7C EB Meaning ‘n’ ‘o’ ‘c’ ‘a’ ‘l’ EOT Chk. Sum

Result: Reply data contains the base alarm message of “Timeperiod no cal”. See next action to find out the additional character following the base message.

MODBUS Action 1 of 1: Obtain alarm text code and qualifier by reading MODBUS register 1010:

Transmit 02 03 03 F2 00 02 65 8F

Meaning Slv. Fn. Reg ID Reg Cnt. Chk sum

Receive 02 03 04 00 0B 31 20 65 8F

Meaning Slv. Fn. D.C. The data Chk sum

Result: 0x000B = A code for the alarm text – not to be confused with the alarm entry ID (from earlier) 0x31 = Represents ASCII character “1” – for metering-point/stream/channel one 0x20 = Alarm Type ‘2’ (2 = Present) + Alarm State ‘0’ (0 = Alarm Not Accepted)

Other possible results… Type of alarm: “0”=Off, “1”=On, “2”=Present State of alarm: “0”=Not Accepted, “1”=Accepted


7951 2510 (Ch07/FC) Page 7.19

MODBUS Action 1 of 1: Retrieve time and date of selected alarm by reading MODBUS register 1009

Transmit 02 03 03 F1 00 08 15 88 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 02 03 10 00 21 00 06 00 0D 00 0A 07 CE 00 1C Meaning Slv. Fn. DC The Data

Receive 00 04 01 2D 32 6B Meaning The Data Chk. Sum

Result: When viewing the Historical Alarm Log entry you would see “28-10-98 13:06:33” on the third line

Special Notes: The order of date/time character strings in packets are unaffected by the ‘word order’ mode.

Step 5 is to accept the alarm that was selected in step three.

MODBUS Action 1 of 1: Write 0x0000 to MODBUS register 1004

Transmit 02 10 03 EC 00 01 02 00 00 97 0C Meaning Slv. Fn. Reg. ID Reg. Cnt. DC The Data Chk. Sum

Receive 02 10 03 EC 00 01 C0 4B Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Result: The alarm entry selected through register 999 has been accepted. Information, such as the base alarm message, remains available until another alarm entry is selected.

Step 6 is to clear the alarm that was selected in step three.

MODBUS Action 1 of 1: Write 0x01 to MODBUS register 1004 (0x3EC)

Transmit 0B 10 03 EC 00 01 02 00 01 56 CC

Meaning Slv. Fn. Reg. ID Reg. Cnt. DC The Data Chk. Sum

Receive 0B 10 03 E7 00 01 C0 4B

Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Result: The alarm (selected through register 999) has been cleared. However, the conditions that caused the

alarm may still be present and the same alarm would then be raised with a new identification number. Information such as the alarm text is now unavailable.


Page 7.20 7951 2510 (Ch07/FC)

7.7.2.2 Example 2 (of 3)

Objective: Clear all alarms from the Historical Alarm Log

MODBUS Action: Write 0x01 to MODBUS register 2001

Transmit 02 10 07 D1 00 01 02 00 01 17 E1 Meaning Slv. Fn. Reg. ID Reg. Cnt. DC The Data Chk. Sum

Receive 02 10 07 D1 00 01 50 B7 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Result: All alarms cleared. However, the conditions that caused the logged alarms may still be present and so

the same alarms would be raised again, but with new identification numbers.

7.7.2.3 Example 3 (of 3)

Objective: Retrieve abbreviated summary of the Historical Alarm Log

MODBUS Action: Read MODBUS register 2010

Transmit 02 03 07 D9 00 03 D5 77 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 01 03 06 00 00 00 0E 10 00 59 86 Meaning Slv. Fn. DC The Data Chk. Sum

Result: The reply data is interpreted as follows:

0x00 (Byte 1) = Number of system class alarms that have not been accepted = 0 0x00 (Byte 2) = Number of input class alarms that have not been accepted = 0 0x00 (Byte 3) = Number of limit class alarms that have not been accepted = 0 0x0E (Byte 3) = Total number of system class alarms (accepted or otherwise) = 14 0x10 (Byte 5) = Total number of input class alarms (accepted or otherwise) = 16 0x00 (Byte 6) = Total number of limit class alarms (accepted or otherwise) = 0

Note: The reply data is a character string and is therefore unaffected by the ‘word order’ mode.


7951 2510 (Ch07/FC) Page 7.21

7.8 Historical Event Log access over a MODBUS network This section demonstrates how a MODBUS Master can access “LIVE” information from the Historical Event Log of a 7951 MODBUS Slave.

Refer to Chapter 8 if an explanation for the Historical Event Log is required.

7.8.1 Introduction

Information from the Historical Event Log is retrievable through the map of MODBUS registers associated with ‘Virtual Address 1’ (base address + offset of 1).

Warning! It is not advisable to clear or accept events using the front panel while the Historical Event Log is being queried by a MODBUS master. This could otherwise result in the MODBUS master having an in-correct view of the content.

Worked examples are provided to demonstrate the correct method for (1) obtaining details of an event, (2)accepting that event and (3) clearing that event

Every example features objectives, actions, and a result analysis.











Page 7.22 7951 2510 (Ch07/FC)


Unless otherwise stated, all request and response messages shown here use (1) the ‘default word order’ mode, (2) 32-bit single precision encoding and (3) multiple read/write register MODBUS functions. A base address of “01” has been assumed for our examples.

Objectives: 1. Find out how many alarms are in the Historical Event Log. 2. Retrieve identification numbers for recorded (logged) events. 3. Make information available on a specific event. 4. Get further information about the event that was selected in step three. 5. Accept/Clear the event that was selected in step three.

Step 1 is to find out how many events are in the Historical Event Log.

MODBUS Action 1 of 1: Read MODBUS register 11,999

Transmit 02 03 2E DF 00 01 BC EB Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 02 03 02 00 96 7C 2A Meaning Slv. Fn. DC The Data Chk. Sum

Result: Returned data indicates that there are 150 (0x0096) events in the Historical Event Log.

Step 2 is to retrieve identification numbers for recorded (logged) events.

MODBUS Action 1 of 1: Retrieve ID number of the oldest event by reading register 10,000

Transmit 02 03 27 10 00 01 8F 48 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 02 03 02 02 D5 3C BB Meaning Slv. Fn. DC The Data Chk. Sum

Result: Reply indicates that the unique event ID is 0x02D5.

Notes: Identification (ID) numbers of recorded events are available from MODBUS registers 10,000 to 10,149. The ID of the oldest recorded entry in the Historical Event Log is at register 10,000. For the purpose of our worked example, one event identification number is sufficient. In practice, all identification numbers would need to be retrieved and stored for repeating steps.

Step 3 is to make information available about a specific event. This is mandatory for remaining steps.

MODBUS Action 1 of 2: Make information available for the first event Write the event identification number (i.e. 0x02D5) to MODBUS register 10,999

Transmit 02 10 2A F7 00 01 02 02 D5 EC DA Meaning Slv. Fn. Reg. ID Reg. Cnt. DC The Data Chk. Sum

Receive 02 10 2A F7 00 01 B8 10 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Result: Reply indicates that the selection has been made.


7951 2510 (Ch07/FC) Page 7.23

MODBUS Action 2 of 2: Check that information for selected event is now available by read register 10,999

Transmit 02 03 2A F7 00 01 3D D3 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 02 03 02 02 D5 3C BB Meaning Slv. Fn. DC The Data Chk. Sum

Result: Reply indicates that the current event ID is confirmed to be 0x02D5.

Step 4 is to get further information about the event that was selected in step 3. To get information about another event, repeat step 3 but use another event identification number.

MODBUS Action 1 of 1: Retrieve event text length by reading MODBUS register 12,000

Transmit 02 03 2E E0 00 01 8C E7 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 03 03 02 00 14 FC 4B Meaning Slv. Fn. DC The Data Chk. Sum

Result:Reply data indicates that the event text length is 20 bytes (0x0014). At present, the length returned is always 20 bytes. Divide the length by 2 to work out the number of register to request when asking for the event text. Do not assume the event text length will always be 18 bytes.

MODBUS Action 1 of 1: Retrieve event text by reading MODBUS register 11,012

Transmit 02 03 2B 04 00 0A 8D DB Meaning Slv. Fn. Reg. ID Reg. Cnt Chk. Sum

Receive 02 03 14 6D 41 20 4F 2F 50 20 38 20 63

Meaning Slv. Fn. DC The Data... (mA O/P 8 cycle time)

Receive 79 63 6C 65 20 74 69 6D 65 00 3A AD

Meaning The Data… Chk. Sum

Result: Reply data contains the ASCII encoded event text. It is unaffected by the ‘word order’ mode.

MODBUS Action 1 of 1: Retrieve location ID, event type, and event state by reading register 11,010

Transmit 02 03 2B 02 00 02 6C 1C Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 02 03 04 00 72 01 01 A9 78 Meaning Slv. Fn. DC The Data Chk. Sum

Result:0x0072 = Location ID 0114 1st. 0x01 = Type (0x00=Auto, 0x01=User, 0x02=Period) 2nd. 0x01 = State (0x00=Pending, 0x01=Accepted)


Page 7.24 7951 2510 (Ch07/FC)

MODBUS Action 1 of 1: Obtain date/time stamp for the same event by reading MODBUS register 11,009

Transmit 02 03 2B 01 00 08 1C 1B Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 02 03 10 00 04 00 33 00 09 00 06 07 D0 Meaning Slv. Fn. DC = 4 seconds = 51 mins. = 9 hours = June = 2000

Receive 00 08 00 05 00 A0 84 82 Meaning = 8th. (June) = Thursday = 160th. Day Chk. Sum

Result: When viewing the Historical Event Log entry you would see “08-06-00 09:51:04” on the third line

Special Notes: The order of this data packet is unaffected by the ‘word order’ mode.

MODBUS Action 1 of 1: Retrieve event data for the same event by reading MODBUS register 11,011

Transmit 02 03 2B 03 00 19 7D D7 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 02 03 32 45 3B 80 00 … 80 53 Meaning Slv. Fn. DC The Data Chk. Sum

Result: 453B8000 is an 32-bit IEEE number representing 3000.00 (Old = 3000.0) - ignore the other 46 bytes

Special Notes: The order of this data packet is unaffected by the ‘word order’ mode. You must use MODBUS function 3 irrespective of whether port is configured for single register access When the data part of the reply represents an option selection code, the code is in the first byte. You

can retrieve option text by reading 22 bytes from registers 11,013 (old option ) and 11014 (new option)

Step 5 is to clear the selected event from Historical Event Log once all associated data has been retrieved

MODBUS Action 1 of 1: Write value of the clearance code (0x0001) to MODBUS register 11,004

Transmit 02 10 2A FC 00 01 02 00 01 EC 9E Meaning Slv. Fn. Reg. ID Reg. Cnt DC The Data Chk. Sum

Receive 02 10 2A FC 00 01 C9 D2 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Result: Event cleared from the Historical Event Log. All associated data is no longer accessible.

Special Notes: If you wish to just accept the selected event, use the acceptance code 0x0000 To clear all events in the Historical Event Log, write any 16-bit value to MOBUS register 12,001


7951 2510 (Ch07/FC) Page 7.25

7.9 Archive access over a MODBUS network This Section demonstrates how a MODBUS Master can access archives of a 7951 MODBUS Slave. Refer to Chapter 9 if an explanation of Data Archiving is required.

7.9.1 Introduction

Information from Archives is retrievable through the map of MODBUS registers associated with ‘VirtualAddress 4’ (base address + offset of 4).

Worked examples in Section 7.9.2 are provided to demonstrate the correct method for (1) selecting an archive by type, (2) selecting a snapshot in that archive and (3) retrieving values from that snapshot.

Every example features objectives, actions, and a result analysis.







Slv. The MODBUS slave base address. Err. Error code. E.g. 83 = Error reading / Exception. Fn. MODBUS Function code. E.g. 03 = Read multiple registers.

Reg. Cnt Number of registers to read or write / Number of registers read or written. Reg. ID MODBUS Register number.

DC Data Count – The number of bytes of data that follow. The Data Data bytes that contain the useful information. Chk sum Calculated checksum - always two bytes at the end.


Page 7.26 7951 2510 (Ch07/FC)


Unless otherwise stated, all request and response messages shown here use (1) the ‘default word order’ mode, (2) 32-bit single precision encoding and (3) multiple read/write register MODBUS functions.

A base address of “01” (for MODBUS) has been assumed for our examples.

Objectives: 1. Select an archive. 2. Find out how many snapshots are stored in that archive. 3. Select a snapshot within that archive. 4. Retrieve values from that archive.

Step 1 is to select an archive by type and then, optionally, verify it has been selected.

MODBUS Action 1 of 2: Select the Interval Archive by writing 0x02 to MODBUS register number 999

Transmit 05 10 03 E7 00 01 02 00 02 31 86 Meaning Slv. Fn. Reg. ID Reg. Cnt. DC The Data Chk. Sum

Receive 05 10 03 E7 00 01 B0 3E Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Result: Reply indicates that the request was successful

Special Note: Codes – 0x0000 (Alarm Triggered Archive), 0x0001 (Daily Archive), 0x0003 (Manual Trigger Archive)

MODBUS Action 2 of 2: Verify the Archive selection by reading from MODBUS register number 999

Transmit 05 03 03 E7 00 01 35 FD Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 05 03 02 00 02 C8 45 Meaning Slv. Fn. DC The Data Chk. Sum

Result: Reply of 0x02 indicates that the Interval Archive was selected.

Step 2 is to find how many snapshots are stored in the selected archive


Read MODBUS register 39,999

Transmit 05 03 9C 3F 00 01 9B D2 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 05 03 02 00 07 Meaning Slv. Fn. DC The Data

Result: There are presently 7 (0x0007) snapshots in the selected archive.


7951 2510 (Ch07/FC) Page 7.27

Step 3 is to select a snapshot from the selected archive and then, optionally, verify it has been selected.


Select newest snapshot the Archive by writing 0x0000 to MODBUS register 1000

Transmit 05 10 03 E8 00 01 02 00 00 B0 B8 Meaning Slv. Fn. Reg. ID Reg. Cnt. DC The Data Chk. Sum

Receive 05 10 03 E8 00 01 80 3D Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Result: Reply indicates that the request was successful.

Special Note: This snapshot selection will not be reflected in archive parameters displayed within the menu system Other selection codes: 0x0001 (oldest snapshot), 0x0002 (2nd oldest snapshot), etc.


Check on snapshot selection by reading from MODBUS register number 1000

Transmit 05 03 03 E8 00 01 05 FE Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 05 03 02 00 00 49 84 Meaning Slv. Fn. DC The Data Chk. Sum

Result: Reply data 0x0000 indicates that the newest (latest) snapshot is selected.

Special Note: This snapshot selection will not be reflected in archive parameters displayed within the menu system Other selection codes: 0x0001 (oldest snapshot), 0x0002 (2nd oldest snapshot), etc.

Step 4 is to retrieve the newest snapshot value from the first parameter programmed into the archive list.

MODBUS Action 2 of 2: Retrieve first parameter attributes by reading MODBUS register 40000

Transmit 05 03 9C 40 00 02 EA 0B Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 05 03 04 06 04 FF 04 BE 89 Meaning Slv. Fn. DC The Data Chk. Sum

Result: 0x06 = Data Type ‘6’ – IEEE 32-bit floating-point value 0x04 = Data Size – Parameter value stored in 4 bytes 0xFF = Status – No Status Attribute 0x04 = Units of measurement group 4 – Volumetric units

Special Notes: The order of this data packet is unaffected by the ‘word order’ mode. Other MODBUS registers: 40001 (= 2nd. listed parameter), 40002 (= 3rd. listed parameter), etc.


Page 7.28 7951 2510 (Ch07/FC)

MODBUS Action 2 of 2: Retrieve value by reading MODBUS register 2000.

Transmit 05 03 07 D0 00 02 C5 02 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. Sum

Receive 05 03 04 00 0D 46 87 5C 32 Meaning Slv. Fn. DC The Data Chk. Sum

Result: 0x000D4687 is the hexadecimal value for 870,023 (m3)

Special Note: Other MODBUS registers: 2001 (=2nd. listed parameter), 2002 (=3rd. listed parameter), etc.

PEER-TO-PEERCOMMUNICATIONS

(CHAPTER 7 ADDENDUM ‘A’)

Chapter 7(a) Peer-To-Peer Communications Software Version 2510, Issue 4.00 (or higher)

Page 7a.2 Issue: AC

ABOUT THIS ADDENDUM

7a.1 What is the purpose if this addendum? This addendum has been written to provide a guide to the software support for peer-to-peer MODBUS network communications.

To use this guide effectively, it is essential to be familiar with the 7951 keypad functions, moving around the menu system, and editing. (Chapter 5 can help with this)

The data necessary for configuring a measurement/feature can be found in separate parts of the menu structure. A notation has been used as a short method of explaining how to move from the present menu to another menu.

As an example, the notation of <“Configure”>/<“Flow rate”> translates into these steps:

Step 1: Press the MAIN-MENU button

Step 2: Use the DOWN-ARROW (‘V’) button to scroll through pages until the word “Configure” is seen.

Step 3: Press the lettered-button that is alongside the word “Configure”.

Step 4: Use the DOWN-ARROW button to scroll through pages until the word “Flow rate” is seen.

Step 5: Press the lettered-button that is alongside the word “Flow rate”.

Sometimes, it is convenient to use the MAIN-MENU button (especially if lost). However, use of the BACK-ARROW button is a much more common method of returning to a higher menu level.

Note: The menu structure will vary in other software versions and releases.

Software Version 2510, Issue 4.30.00 (or higher) Chapter 7(a) Peer-To-Peer Communications

Issue: AC Page 7a.3

PEER-TO-PEER COMMUNICATIONS INTRODUCTION

7a.2 Feature: 7951 communication of parameters (peer-to-peer lists) An overview is in Section 7a.2.1…………………….……………. Page 7a.3 A list of configuration instructions is in Section 7a.2.2…..…….. Page 7a.5

7a.2.1 What is the purpose of this feature?

This feature is typically used when a ‘Header’ Flow Computer must send various measurements (e.g. pressure, temperature, etc.) over a MODBUS link to one or more ‘Stream’ Flow Computers.

USE OF THE MODBUS PROTOCOL In MODBUS protocol terms, a ‘Header’ Flow Computer is usually given the role of a MODBUS Master device. It has the responsibility for the peer-to-peer transmission of measurement values during every machine cycle. The ‘Stream’ Flow Computers are MODBUS Slave devices, and they receive the peer-to-peer transmissions.

When an RS-232 point-to-point network is used: A 7951 Master device continuously broadcasts values of peer-to-peer nominated parameters directly to the database of a single 7951 Slave device. The two MODBUS devices can be wired together via anyserial port supporting RS-232 standard. A peer-to-peer topology is shown in Figure 7a.1 on page 7a.3.

When an RS-485 multiple-drop network is used: A 7951 Master device continuously broadcasts values of peer-to-peer nominated parameters to a maximum of sixteen 7951 MODBUS slaves. The 7951 MODBUS devices can be wired together via anyserial port supporting the RS-485 standard. A peer-to-peer topology is shown in Figure 7a.2 on page 7a.3

At present, peer-to-peer communications will operate through one serial port. Configuring another serial port of the ‘Header’ 7951 to function as a Master device and connecting it to a duplicate MODBUS network will cause unpredictable results.

THE PEER-TO-PEER LISTS On the 7951 Master there are two peer-to-peer lists 1 for compiling a collection of up to 40 measurement parameters (7951 database locations) in total. The list is simply a look-up reference for the Master, when preparing transmissions, and is programmed with database location IDs. 2

Figure 7a.2 shows how an individual peer-to-peer list comprises entries (parameters) for nominating from 1 up to 20 parameters. Each list entry requires a programmed source – a database location ID on the 7951 Master device - and a programmed destination – a database location ID on the 7951 Slave devices.

661 661

Source(Location IDs)

Destination(Location IDs)

256 662

(Off) (Off)

"IndicatedVolume Rate"

(Off) (Off)"Actual CycleTime"


"GrossVolume Rate"

01

02

03

20

01

02

03

20

Figure 7a.2: Peer-To-Peer List

1 These lists are wholly independent of the High Speed Lists that are set-up on one (or more) 7951 MODBUS slaves for access by

non-7951 MODBUS Master devices. 2 To find out the database location ID for any parameter, navigate the menu system to the applicable parameter and then press the

a-button once. The 4-digit database location ID is then displayed on the fourth line of the LCD display.


Page 7a.4 Issue: AC

INTRODUCTION PEER-TO-PEER COMMUNICATIONS

Each 7951 Slave device is allocated one of the two lists. This is a user-selection and is made when defining slaves whilst setting up the 7951 Master device.

After the lists are programmed, peer-to-peer operations are commenced on the 7951 Master by a selecting an “Enable” option (‘menu-based command’) through a parameter. For each correctly listed parameter, a value is then read from the database, incorporated into a MODBUS ‘write’ command message and transmitted from the 7951 Master device to the database on designated 7951 Slave devices.

All peer-to-peer lists, in use, are processed in full during a single machine cycle. This is repeated once every cycle until peer-to-peer operations are stopped by a “disable” command.

In a network of two 7951 Flow Computers – a Master device and a Slave device, the Master is able to detect all failures to communicate with the slave and it raises a system alarm. With one slave, every MODBUS (‘write’) command message is explicitly addressed and that solicits a response from that slave. The absence of a response after a period (of retries) is how the Master detects a failure3.

In a network of multiple slaves, MODBUS ‘write’ command messages use an all-slave broadcast address,which does not solicit any response and, therefore, the Master does not detect a communication failure. In this case, the system alarm is not raised.

When the system alarm can not be cleared without it re-appearing during the next machine cycle, there are continuous communication failures. It is advisable to temporarily halt peer-to-peer operations, clear all related alarms and investigate (and correct) the difficulty before resuming.

LIST ONE

7951 MODBUS Master Device

LIST TWO

DATABASE

DATABASE

DATABASE

DATABASE

7951 MODBUS Slave Device 1



P2

P3

P2

P3

RS-485LINK

MODBUS Commands

LogicalLink

Figure 7a.1: Peer-To-Peer - Basic RS232 Arrangement

LIST ONE

7951 MODBUS Master Device

LIST TWO

DATABASEDATABASE 7951 MODBUS Slave Device 1P1 P2RS-232

MODBUS Commands

LINK

LogicalLink

Figure 7a.2: Peer-To-Peer - Basic RS485 Arrangement

3 This type of failure is normally the symptom of a faulty/unsuitable cable, incorrect set-up of communication parameters or the

absence of a physical connection to a MODBUS network.

Software Version 2510, Issue 4.30.00 (or higher) Chapter 7(a) Peer-To-Peer Communications

Issue: AC Page 7a.5

PEER-TO-PEER COMMUNICATIONS INSTRUCTIONS

7a.2.2 Configuring and activation instructions

Follow these instructions to configure and activate peer-to-peer communications…

1. Ensure that 7951 Flow Computers are already interconnected to form a MODBUS network

Guidance on the necessary RS-232 or RS-485 wiring 4 connections is in Chapter 7. Several peer-to-peer arrangements are shown on page 7a.4.

2. Program a 7951 Flow Computer to be the MODBUS master device

(2a) Navigate to this menu: <”Configure”>/<”Other Parameters”>/<”Communications”>/<”Ports”>

(2b) Select the menu for the serial port that is connected to the MODBUS network

(2c) Program the basic communications parameters for that serial port, as shown in Table 7a.1. Some localised menu searching is required.

Table 7a.1: Basic Serial Port Communication Parameters

Parameters * Instructions and Comments

Comms port owner Select the option with “Modbus master” as the description Port Baud rate Select a rate that is agreed for the 7951 Master device and all the slaves devices

Port char format Select a character transmission format (as agreed for the MODBUS network) Port handshaking Select either “None” or “XonXoff” unless the cable (wiring) supports “CTS/RTS” Port RS232 / 485 Select the signalling standard for the MODBUS network **

P Modbus word order *** Not applicable to the 7951 Master device Port Modbus mode Select the option that is compatible with the other MODBUS network devices.

P MODB slave addr *** Not applicable to a 7951 Master device. The existing setting does not affect it. P Modbus features Not applicable to a 7951 Master device. The existing setting does not affect it.

P long reg access *** Choose either single register or multiple register formatted MODBUS commands P MODB precision *** Choose a precision option that is agreed for the Master and all the slaves devices

* On-screen version of a parameter descriptor includes a digit to identify the directly associated serial port

** A 7951 may perform ‘warm restarts’ if it is configured to use RS-232 when connected to an RS-485 network

*** Abbreviations: “P ” = Port, “reg” = register, “addr” = address, “char” = character, “MODB” = MODBUS

(2d) Navigate to this menu: <”Configure”>/<”Other Parameters”>/<”Communications”>/<”Modbus master”>/<”Peer to peer”>

(2e) Program the peer-to-peer lists

Menus:

Peer List One: <Configure”>/…<”Modbus master”>/<”Peer to Peer”>/<”Peer list 1”> Peer List Two: <Configure”>/…<”Modbus master”>/<”Peer to Peer”>/<”Peer list 2”>

When programming a list, it is very important to use the first available (unused) entry and to not leave gaps. This will avoid inadvertently shortening the list.

Programming a valid location number for a source will immediately result in the number changing to the parameter descriptor. The destination does not do this because the edited location number stays displayed as the edited number. Editing a location number for a parameter that does not exist is responded with a “*** ERROR ***” message appearing briefly and the original setting is then restored.

4 To avoid the risk of ‘unexpected restarts’, it is advisable to pre-set the signalling standard – RS-232 or RS-485 – for 7951 serial

ports before establishing the physical connections.

CONNECTING MORE THAN ONE SERIAL PORT TO THE A PEER-TO-PEER MODBUS NETWORK WILL CAUSE UNPREDICTABLE RESULTS


Page 7a.6 Issue: AC

INSTRUCTIONS PEER-TO-PEER COMMUNICATIONS

By default, destinations (location IDs) are automatically synchronised with the corresponding sources. This is ideal for when Flow Computers are running the same software release. However, the source and destination (IDs) do not have to be the same. For each list, there is a peer-to-peer configuration parameter, <Peer L dest/src>, to stop the synchronising action and enable IDs to be different. This feature allows 7951 slave devices to run releases other software versions and still get updates from the Master device. Re-enabling the synchronising will immediately trigger the overwriting of all destination IDs with the source IDs, losing the destination IDs forever.

Values go directly into the 7951 database of a slave unless serial communications is prohibited. Security parameters for serial communications are found within <”Configure”>/<”Other parameters”>/<”Security”>.

(2f) Inform the 7951 Master about all 7951 slave devices on the network: (Note: Start by programming details of your first slave using parameters within the “Device 1” menu)


Slave device func ** Select the option with “Peer” as the description. Slv device port no ** Select the serial port that is connected to same the network as the slaveSlv device address ** Use “0” if there are multiple slaves. Otherwise, use the address of the slave

Device word swap Not applicable to the 7951 but may be needed by protocol listening devicesDevice precision Use a precision option that is the same as the 7951 MODBUS Master Device peer list Select the option that corresponds to one of the two peer-to-peer lists

* On-screen version of parameter descriptor includes a digit to identify the directly associated serial port ** Abbreviations: “Slv” = Slave, “func” = Function, “no” = number

3. Program each remaining 7951 to be a MODBUS slave device (3a) Navigate to this menu: <”Configure”>/<”Other Parameters”>/<”Communications”>/<”Ports”>(3b) Select a menu that corresponds to the serial port that is connected to the RS-485 network (3c) Set-up basic communications parameters:


Comms port owner Select the option with “Modbus slave” as the description. Port Baud rate Select a rate that is compatible with the other MODBUS network devices.

Port char format *** Select a rate that is compatible with the other MODBUS network devices.Port handshaking Select the same option as used for the 7951 Master device. Port RS232 / 485 Select the signalling standard for the MODBUS network. **

P Modbus word order *** Select the option that is compatible with the other MODBUS network devices. Port Modbus mode Select the option that is compatible with the other MODBUS network devices.

P MODB slave addr *** Edit a value that does not conflict with other MODBUS network devices.P Modbus features *** Not applicable to peer-to-peer operations. P long reg access *** Select the same option as used for the 7951 Master device.P MODB precision *** Select the same option as used for the 7951 Master device.

* On-screen version of parameter descriptor includes a digit to identify the directly associated serial port ** A 7951 may perform ‘warm restarts’ if it is configured to use RS-232 when connected to an RS-485 network


4. Start peer-to-peer communications at the 7951 Master device (4a) Navigate to: <”Configure”>/<”Other Parameters”>/<”Communications”>/<”Modbus master”> (4b) Locate the parameter with “Peer enable” on-screen (4c) Select the “Enable” menu-based command (option)

Once enabled, it is advisable to stop (deactivate) peer-to-peer communications prior to adjusting the communications set-up. Once changes have been made, re-enable the peer-to-peer function with step 4.

HIGH-SPEED LIST COMMUNICATIONS

(CHAPTER 7 ADDENDUM ‘B’)

Chapter 7(b) HSL Communications Software Version 2510, Issue 4.30.00 (or higher)

Page 7b.2 Issue: AC

ABOUT THIS ADDENDUM

7b.1 What is the purpose if this addendum? This addendum has been written to provide a guide to the software support for HSL - High Speed List – communications over a MODBUS protocol network.

To use this guide effectively, it is essential to be familiar with the 7951 keypad functions, moving around the menu system and editing. (Chapter 5 can help with this)

The data necessary for configuring a measurement/feature can be found in separate parts of the menu structure. A notation has been used as a short method of explaining how to move from the present menu to another menu.







Sometimes, it is convenient to use the MAIN-MENU button (especially if lost). However, use of the BACK-ARROW button is a much more common method of returning to a menu level.


Software Version 2510, Issue 4.30.00 (or higher) Chapter 7(b) HSL Communications

Issue: AC Page 7b.3

INTRODUCTION HIGH-SPEED LIST COMMUNICATIONS

7b.2 Communication of parameter data using High-speed Lists An overview is in Section 7b.2.1…………..…………………………….. Page 7b.2

A list of configuration instructions is in Section 7b.2.2………..……... Page 7b.9

A guided example in Section 7b.2.3……………………..…...………… Page 7b.13

Wonderware compatibility notes are in Section 7b.3………….……….. Page 7b.19

7b.2.1 What is the purpose of High-speed Lists?

This feature is typically used when a MODBUS Master device 1 must get parameter data from a 7951 Flow Computer, where both are attached to the same MODBUS protocol network.

High-speed list communications facilitate the quick collection and transmission of data from up to 300 user-nominated parameters. This is achieved by using just a small quantity of MODBUS protocol messages. It would otherwise require an exchange of hundreds of messages.

The 7951 Flow Computer also helps by collecting data of nominated (listed) parameters from its’ database and keeping it ‘localised’. This activity is completed during every machine cycle. Keeping parameter data ‘locally’ allows faster data access, allowing the 7951 to service requests from a Master device as quickly as possible.

There are two aspects to high-speed list communications:

The MODBUS protocol (network arrangements, communication parameters, and message exchanges). A list of parameters (i.e. 7951 database locations).

USE OF THE MODBUS PROTOCOL In MODBUS protocol terms, the MODBUS Master device is likely to be a supervisory system. The Master device is responsible for acquiring parameter data through an exchange of MODBUS protocol messages with one ore more a MODBUS networked slave devices. The 7951 Flow Computer is the MODBUS slave device, supporting RS-485 and RS-232 signalling standards.

When an RS-232 point-to-point network is used: A Master device can request parameter data from one 7951 slave device. The two MODBUS devices can be wired together via any serial port supporting RS-232 Standard (see Figure 7b.1).

High Speed List One(Virtual Slave 2)

7951 MODBUS Slave Device

APPLICATIONDATABASE

MODBUS Master Device

P1 P2RS-232

MODBUS Messages

LINK

Read/Write Database

Operations

High Speed List Two(Virtual Slave 3)

Direction of flow (HSL Data)

Figure 7b.1: High Speed List Overview (RS-232 Example)

1 This MODBUS Master device cannot be a 7951 Flow Computer. Direct communication of a parameter value between 7951 Flow

Computers can be performed using the “Peer-To-Peer Lists” feature.


Page 7b.4 Issue: AC

HIGH-SPEED LIST COMMUNICATIONS INTRODUCTION

When an RS-485 multiple-drop network is used: A Master device can request parameter data from one or more 7951 slaves. The 7951 slave devices can be wired together via any serial port supporting the RS-485 Standard (see Figure 7b.2).

High Speed List 1(Virtual Slave '2')


APPLICATION

DATABASE

MODBUS Master Device

P2

SerialPort

RS-485Link

MODBUS Messages

Read/Write Operations

Direction of flow (HSL Data)



DATABASEP3



Figure 7b.2: High Speed List Overview (RS-485 Example)

THE HIGH-SPEED PARAMETER LIST On 7951 slaves there are two individual lists 2 for nominating the parameters – labelled as “High Speed List 1”and “High Speed List 2” within the communications area of the menu system.

Each list has the capacity for nominating up to 150 parameters, organised into three blocks of 50 parameters. Figure 7b.3 illustrates the three block structure for both lists. The blocks are set-up on an individual basis. Parameters are nominated using their own unique database location identification (ID) number. Each entry in a block has a dedicated software parameter for editing in a location ID.

HIGH SPEED LIST TWO

661 0718

BLOCK A(Location IDs)

HIGH-SPEED LIST ONE

662 0595

(Off) (Off)

IndicatedVolumeflow rate

(Off) 1548GrossVolumeflow rate

01

02

03

50

01

02

03

50

(Off)(Off)

(Off)

(Off)

01

02

03

50

BLOCK B(Location IDs)

BLOCK C(Location IDs)

(Off) = Unused Entry

2048 (Off)

BLOCK D(Location IDs)

2111 (Off)

(Off) (Off)

PrimeDynamicViscosity

(Off) (Off)PrimeKinematicViscosity

01

02

03

50

01

02

03

50

(Off)(Off)

(Off)

(Off)

01

02

03

50

BLOCK E(Location IDs)

BLOCK F(Location IDs)


Figure 7b.3: Parameter List Block Organisation

The parameter list is primarily for the 7951 slave device to extract data of specific parameters from its’ database during every machine cycle. All extracted data is stored ‘locally’ for faster and more efficient data access. It is then accessible only to a Master device by means of MODBUS ‘read’ command messages. Figure 7b.4 illustrates the process.

2 These lists are wholly independent of the peer-to-peer lists that are set-up on a 7951 MODBUS Master device.


Issue: AC Page 7b.5


LIST ONE


LIST TWO

DATABASECopying Activity

Every Cycle

Loc ID: 0661450.015V

S Live

1Loc ID: 0662

448.011VS Live

2Loc ID: 0000

-VS -

3Loc ID: 0000

-VS -

50

Loc ID: 0661450.015V

S Live

Loc ID: 0662448.011V

S Live

Loc ID: 0663-V

S -

7951 DATABASE

HIGH SPEED LIST ONE

Figure 7b.4: High-speed list activity within 7951 Slave Devices

MODBUS ‘read’ command messages must be addressed to either virtual slave ‘2’ or virtual slave ‘3’ through any MODBUS slave configured port. Virtual slave addressing is explained in Chapter 7.

MODBUS Address Information Available

Virtual Slave ‘2’ High-speed List One Virtual Slave ‘3’ High-speed List Two

The Modbus register map of virtual slave 2 and 3 are initially in a pre-set format but it can individually re-organised to suit applications on the Master device. There are several pre-set formats available for selection. Follow the links in Table 7b.1 to get a graphical overview of default Modbus register map for each pre-set format. You will also get to see how the blocks of a parameter list are linked to a Modbus register map.

Table 7b.1: Links to graphical overviews of high-speed lists and register maps

Pre-set Format Graphical Representation

Old Style (Legacy) * See Figure 7b.5 on page 7b.6Grouped See Figure 7b.6 on page 7b.7

Ungrouped See Figure 7b.7 on page 7b.8

* As found in 7951 software released before the year 2000


Page 7b.6 Issue: AC


Values

Location IDs

Status

1001

11001

21001Types and Sizes

Full Attributes

31001

41001

BLOCK 'E' SECTIONS(VIRTUAL SLAVE 3 REGISTER MAP)

Block D Block E Block F HIGH-SPEED LIST 2

HSL-2 BLOCK E

HSL ONE

HSL-2 BLOCKS

HSL TWO

1050

11050

HIGH-SPEEDLISTS

21050

31050

41050

Values

Location IDs

Status

1

10001


Full Attributes

30001

40001

BLOCK 'D' SECTIONS(VIRTUAL SLAVE 3 REGISTER MAP)

HSL-2 BLOCK D

50

10050

20050

30050

40050

Values

Location IDs

Status

2001

12001


Full Attributes

32001

42001

HSL-2 BLOCK F

2050

12050

22050

32050

42050

BLOCK 'F' SECTIONS(VIRTUAL SLAVE 3 REGISTER MAP)

VIRTUAL SLAVE 2

VIRTUAL SLAVE 3

Block A Block B Block C HIGH-SPEED LIST 1HSL-1 BLOCKS

Values

Location IDs

Status

1001

11001


Full Attributes

31001

41001

BLOCK 'B' SECTIONS(VIRTUAL SLAVE 2 REGISTER MAP)

HSL-1 BLOCK B

1050

11050

21050

31050

41050

Values

Location IDs

Status

1

10001


Full Attributes

30001

40001

BLOCK 'A' SECTIONS(VIRTUAL SLAVE 2 REGISTER MAP)

50

10050

20050

30050

40050

Values

Location IDs

Status

2001

12001


Full Attributes

32001

42001

BLOCK 'C' SECTIONS(VIRTUAL SLAVE 2 REGISTER MAP)

2050

12050

22050

32050

42050

HSL-1 GroupedStart Register = 0

HSL-1 BLOCK A HSL-1 BLOCK C


51 - 1000

are unused1051 - 2000

are unused

2051 - 10000are unused

2051 - 10000are unused

51 - 1000

are unused 1051 - 2000

are unused

BLOCK APARAMETER LIST

0102

50

BLOCK BPARAMETER LIST

0102

50

BLOCK CPARAMETER LIST

0102

50

BLOCK DPARAMETER LIST

0102

50

BLOCK EPARAMETER LIST

0102

50

BLOCK FPARAMETER LIST

0102

50

Figure 7b.5: Default Register Mappings for "Old Style" High-speed Lists 1 and 2


Issue: AC Page 7b.7


Values

Location IDs

Status

50

200

350Types and Sizes

Full Attributes

500

650



HSL-2 BLOCK E

HSL ONE

HSL-2 BLOCKS

HSL TWO

99

249

HIGH-SPEEDLISTS

399

549

699

Values

Location IDs

Status

0

150

300Types and Sizes

Full Attributes

450

600


HSL-2 BLOCK D

49

199

349

499

649

Values

Location IDs

Status

100

250

400Types and Sizes

Full Attributes

550

700

HSL-2 BLOCK F

149

299

449

599

749


VIRTUAL SLAVE 2

VIRTUAL SLAVE 3


Values

Location IDs

Status

50

200

350Types and Sizes

Full Attributes

500

650


HSL-1 BLOCK B

99

249

399

549

699

Values

Location IDs

Status

0

150

300Types and Sizes

Full Attributes

450

600


49

199

349

499

649

Values

Location IDs

Status

100

250

400Types and Sizes

Full Attributes

550

700

BLOCK 'C' SECTIONS (VIRTUALSLAVE 2 REGISTER MAP)

149

299

449

599

749





0102

50


0102

50


0102

50


0102

50


0102

50


0102

50

Figure 7b.6: Default Register Mappings for "Grouped" High-speed Lists 1 and 2


Page 7b.8 Issue: AC


Values

Location IDs

Status

250

300

350Types and Sizes

Full Attributes

400

450



HSL-2 BLOCK E

HSL ONE

HSL-2 BLOCKS

HSL TWO

299

349

HIGH-SPEEDLISTS

399

449

499

Values

Location IDs

Status

0

50

100Types and Sizes

Full Attributes

150

200


HSL-2 BLOCK D

49

99

149

199

249

Values

Location IDs

Status

500

550

600Types and Sizes

Full Attributes

650

700

HSL-2 BLOCK F

549

599

649

699

749


VIRTUAL SLAVE 2

VIRTUAL SLAVE 3


Values

Location IDs

Status

250

300

350Types and Sizes

Full Attributes

400

450


HSL-1 BLOCK B

299

349

399

449

499

Values

Location IDs

Status

0

50

100Types and Sizes

Full Attributes

150

200


49

99

149

199

249

Values

Location IDs

Status

500

550

600Types and Sizes

Full Attributes

650

700

BLOCK 'C' SECTIONS(VIRTUAL SLAVE 2 REGISTER MAP)

549

599

649

699

749





0102

50


0102

50


0102

50


0102

50


0102

50


0102

50

Figure 7b.7: Default Register Mappings for "Ungrouped" High-speed Lists 1 and 2


Issue: AC Page 7b.9

HIGH-SPEED LIST COMMUNICATIONS INSTRUCTIONS

7b.2.2 Configuring and Activation Instructions

Follow these instructions to configure and activate high-speed list communications:

1. Ensure that 7951 Flow Computers are already interconnected to form a MODBUS network.

Guidance on the necessary RS-232 or RS-485 wiring 3 connections is in Chapter 7.

2. Program a 7951 Flow Computer to be the MODBUS slave device

(2a) Navigate to this menu: <”Configure”>/<”Other Parameters”>/<”Communications”>/<”Ports”>.

(2b) Select the menu that is appropriate for the serial port that is connected to the MODBUS network.

(2c) Edit the basic communications parameters for that serial port, as shown in Table 7b.2. (Some localised menu navigation is required.)

Table 7b.2: Basic Serial Port Communication Parameters


Comms port owner Select the option with “Modbus slave” as the description.

Port Baud rate Select a rate that is agreed for the Master device and all the 7951 slaves devices.

Port char format Select a character transmission format (as agreed for the MODBUS network).

Port handshaking Select either “None” or “XonXoff” unless the cable (wiring) supports “CTS/RTS”.

Port RS232 / 485 Select the signalling standard for the MODBUS network. **

P Modbus word order *** Select an option that is compatible with the Master device.

Port Modbus mode Select the option that is compatible with the other MODBUS network devices.

P MODB slave addr *** Program the base address of this slave.

P Modbus features Select an option that includes “L1”/“List1” for HSL-1 and “L2”/“List2” for HSL-2.

P long reg access *** Choose to accept either the single or multiple register MODBUS command format

P MODB precision *** Select a precision option that is compatible with the Master device.

* On-screen version of a parameter descriptor includes a digit to identify the directly associated serial port ** A 7951 may perform ‘warm restarts’ if it is configured to use RS-232 when connected to an RS-485 network


3. Program High Speed List ‘1’ (if applicable)

(3a) Navigate to this menu: <”Configure”>/<”Other Parameters”>/<”Communications”>/<”Modbus slave”>.

(3b) Select the menu that is appropriate for HSL-1.

(3c) Edit the configuration parameters for HSL-1, as guided in Table 7b.3.

Table 7b.3: HSL-1 Configuration Parameters (Part One)

Parameters (as displayed) Instructions and Comments

List 1 word order This selection overrides the serial port setting

List 1 block layout Select default register map organisation: “Old Style”, “Grouped” or “Ungrouped” *

L1 grouped start reg Program the number of the first register space for the complete register map **

* See pages 7b.6, 7b.7 and 7b.8 for a graphical view of the default register map for each selectable style

3 To avoid the risk of ‘warm restarts’, it is advisable to pre-set the signalling standard – RS-232 or RS-485 – for 7951 serial ports

before establishing the physical connections.


Page 7b.10 Issue: AC


(3d) View/Edit the number of the first register for each register map section in ‘Block A’ (if applicable)

Note: This step does not apply when the “Old Style” (legacy) register map layout is chosen in step 3c.

Table 7b.4 lists the software parameters for viewing and editing a pre-set Modbus register map for ‘Block A’. Alongside the parameters are default settings for every selectable pre-set format for the block layout. Editing of the Start registers is only required when the default settings form a Modbus register map that is unsuitable for the application on the Master device.

Table 7b.4: Configuration Parameters for Section Start Registers of HSL-1 Block A

Parameters (as displayed)

Default Start Registers (“Old Style” mapping)

Default Start Registers(“Grouped” mapping)

Default Start Registers (“Ungrouped” mapping)

L1A vals start reg 1 0 0

L1A locs start reg 10001 150 50

L1A types start reg 20001 300 100

L1A status start reg 30001 450 150

L1A attrs start reg 40001 600 200

Note: Also see Table 7b.5 and Table 7b.6 for the default settings of the other HSL-1 blocks

(3e) View/Edit the number of the first register for each register map section in ‘Block B’ (if applicable)

Note: This step does not apply when “Old Style” (legacy) register map has been chosen in step 3c.

Table 7b.5 lists software parameters for viewing and editing a pre-set Modbus register map for ‘Block B’. Alongside the parameters are default settings for every selectable pre-set format for the block layout. Editing of the Start registers is only required when the default settings form a Modbus register map that is unsuitable for the application on the Master device.

Table 7b.5: Configuration Parameters for Section Start Registers of HSL-1 Block B

Parameters *(as displayed)

Default Start Registers (“Old Style” map)

Default Start Registers(“Grouped” map)

Default Start Registers (“Ungrouped” map)

L1B vals start reg 1001 50 250

L1B locs start reg 11001 200 300

L1B types start reg 21001 350 350

L1B status start reg 31001 500 400

L1B attrs start reg 41001 650 450

Note: Also see Table 7b.4 and Table 7b.6 for the default settings of the other HSL-1 blocks

(3f) View/Edit the number of the first register for each register map section in ‘Block C’ (if applicable)

Note: This step does not apply when “Old Style” (legacy) register map has been chosen in step 3c.

Table 7b.6 lists software parameters for viewing and editing a pre-set Modbus register map for ‘Block C’. Alongside the parameters are default settings for every selectable pre-set format for the block layout. Editing of the Start registers is only required when the default settings form a Modbus register map that is unsuitable for the application on the Master device.


Issue: AC Page 7b.11


Table 7b.6: Configuration Parameters for Section Start Registers of HSL-1 Block C

Parameters *(as displayed)

Default Start Registers (“Old Style” map)

Default Start Registers(“Grouped” map)

Default Start Registers (“Ungrouped” map)

L1C vals start reg 2001 100 500

L1C locs start reg 12001 250 550

L1C types start reg 22001 400 600

L1C status start reg 32001 550 650

L1C attrs start reg 42001 700 700

Note: Also see Table 7b.4 and Table 7b.5 for the default settings of other HSL-1 Blocks

(3g) Edit the high-speed list with the location ID of each parameter to be made available to the Master.

Table 7b.7 lists the parameters for populating ‘Block A’ with location IDs of up to 50 parameters. The parameters for editing entries in ‘Block A’, ‘Block B’, and ‘Block C’ are located within the 7951 menu system under the respective sub-menus of <“Block A”>, <“Block B”>, and <“Block C”>.

Table 7b.7: ‘BLOCK A’ Parameter Entries 1–50

Parameters(as displayed)

Purpose

DBM list 1A ptr 1 * BLOCK A PARAMETER LIST ENTRY 1 DBM list 1A ptr 2 * BLOCK A PARAMETER LIST ENTRY 2

: : DBM list1A ptr 50 * BLOCK A PARAMETER LIST ENTRY 50

* Abbreviation: “ptr” = pointer (a programming term)

It is good practice to start with ‘Block A’ before progressing to ‘Block B’. Likewise, start with ‘Block B’ before progressing to ‘Block C’.

When programming in location identification numbers (IDs), it is very important to use the first available (unused) entry, and to not leave gaps. This will avoid inadvertently shortening the list (see Figure 7b.8). However, it is not necessary to fully utilise a block before using another.

661 0718


HIGH SPEED LIST '1'(Programmed Correctly)

662 0595

(Off) (Off)


(Off) 1548"GrossVolume Rate"

01

02

03

50

01

02

03

50

(Off)(Off)

(Off)

(Off)

01

02

03

50




661 0718


(Off) (Off)

(Off) (Off)


662 0595"GrossVolume Rate"

01

02

03

50

01

02

03

50

(Off)(Off)

(Off)

(Off)

01

02

03

50




HIGH SPEED LIST '1'(Programmed Incorrectly)

Figure 7b.8: Correct and Incorrect Programmed Parameter Lists




Editing in a valid location number will immediately result in the number changing to the parameter descriptor. Editing a location number for a parameter that does not exist is responded with a “** ERROR **” message appearing briefly, and the original setting is then restored.

4. Edit High Speed List ‘2’ (if it is to be used )

Repeat steps 3a to 3g, but this time it is for configuring HSL-2.



HIGH-SPEED LIST COMMUNICATIONS GUIDED EXAMPLE

7b.2.3 Guided Example: accessing a HSL over a MODBUS network

This section is a practical guide to collecting parameter data from a 7951 MODBUS Slave through the high-speed list feature. For this guided example, High-speed List ‘1’ (HSL-1) has been used.

1. Review the 7951 slave configuration

Table 7b.9 and Table 7b.10 show configuration details for this guided example. These checklists should be used in conjunction with the “Instructions” section on page 7b.9.

MODBUS feature settings for the serial port have been chosen especially to obtain the MODBUS message sequences that are shown later. For a full list of configuration parameters for serial communications, please refer to the “Instructions” section on page 7b.9.

For the purpose of this guided example, instructions assume that the Master device is already set-up.

2. Review the MODBUS message sequences

MODBUS message sequences aim to show the best approach to accessing high-speed list parameter data through a MODBUS register map at a virtual slave address. For this guided example, the “Old Style” default register map has been used.

Every example features an objective, an action and a result.

Objective(s) For an example, the objective could be to read a value from two listed parameters.

Action(s) Actions consist of one or more ‘read’ and ‘write’ MODBUS protocol commands. They are represented in this documentation as tabulated hexadecimal values in sequence for transmission by the Master device. Expected replies from the 7951 MODBUS slave device are also shown as tabulated values.

Table 7b.8 is a list of all the abbreviations of meanings that can appear with a sequence. Use them to distinguish the important elements of the message.

Result This is a brief analysis of the MODBUS slave response to an action. There may be a reference to additional information.

Table 7b.8: Abbreviations for Interpreting Elements of Transmit and Receive Sequences

Abbreviation Meaning

Slv. Virtual slave address. It is 0x03 for this guided example.

Err. Error code. E.g. 83 = Error reading / Exception.

Fn. Function code. E.g. 03 = Read multiple registers.

Reg. Cnt Number of registers requested.

Reg. ID MOBUS register number.

DC Number of ‘data bytes’ in reply.

The Data Data bytes that contain the useful information.

Chk sum Calculated checksum - always two bytes at the end.



GUIDED EXAMPLE HIGH-SPEED LIST COMMUNICATIONS

Table 7b.9: HSL-1 Set-up for Guided Example

Parameters Value/Option Comment

List 1 word order “Modbus default” List 1 block layout “Old-style” The register map for this example is shown in Figure 7b.9.

L1 grouped start reg 0 DBM list 1A ptr 1 0661 ID is for Indicated Volume flow rate DBM list 1A ptr 2 0662 ID is for Gross Volume flow rate DBM list 1A ptr 3 0000 ID is for “Off” - terminates the parameter list for Block A DBM list 1B ptr 1 0773 ID is for integer part of the Indicate Volume flow total DBM list 1B ptr 2 0772 ID is for fractional part of the Indicate Volume total DBM list 1B ptr 3 0779 ID is for integer part of the Gross Volume flow total DBM list 1B ptr 4 0778 ID is for fractional part of the Gross Volume flow total DBM list 1B ptr 5 0000 ID is for “Off” - terminates the parameter list for Block B DBM list 1C ptr 1 0000 ID is for “Off” - terminates the parameter list for Block C

Notes: 1. Metering totals are stored in the database in two parts. There is one database location for the integer part and

one database location for the fractional part. They are usually not displayed within the menu system. When communicating totals over MODBUS, transmit both the integer and fractional values. All totals displayed within the menu system are also database locations. However, they are not suitable for transmission.

2. Abbreviations: “L1” = ‘High-speed List 1’, “reg” = register, “DBM” = Database Manager, “ptr” = pointer. 3. Location identification numbers (IDs) and descriptors may differ to those listed here if you are using a later

software release.

Table 7b.10: Serial Port Set-up for Guided Example

Parameters * Value/Option Comments

Comms port owner “Modbus slave” P Modbus word order Modbus default Port Modbus mode “RTU” P MODB slave addr 1 This is the base slave address. P Modbus features “Alarm+List1+List2” Enables virtual slaves 1, 2 and 3. P long reg access “Single register” Request 1 register per parameter. P MODB precision “Single” Require 32-bit floating-point values

* Location descriptors may differ to those listed here if you are using a later software release

Values

Location IDs

Status

1001

11001


Full Attributes

31001

41001

BLOCK 'B' SECTIONS(REGISTER MAP)

Block A Block B Block C

HIGH-SPEED LIST

HSL 1 BLOCK B

HSL ONEHSL BLOCKS

HSL TWO

1050

11050

HIGH-SPEEDLISTS

21050

31050

41050

Values

Location IDs

Status

1

10001


Full Attributes

30001

40001


HSL-1 BLOCK A

50

10050

20050

30050

40050

Values

Location IDs

Status

2001

12001


Full Attributes

32001

42001

BLOCK 'C' SECTIONS(REGISTER MAP)

HSL 1 BLOCK C

2050

12050

22050

32050

42050

51 - 1000

are unused1051 - 2000

are unused

Figure 7b.9: Register Map for Guided Example 1




MODBUS MESSAGE SEQUENCES:All transmit and receive sequences, shown here, demonstrate use of default word ordering, single precision (32-bit) data representation and ‘single register’ formatted commands. Transmitted messages are addressed to the second virtual slave (base slave address + 2) for access to the “Old style” default register map of High-speed List 1.

(1a) Objective: Read values from all of the parameters listed in High-speed List One (HSL-1)

Action 1 of 3: Read two registers starting from MODBUS register 1 (Values Section, ‘Block A’) Values expected in the reply are 3600.125 and 3546.123, both in base units of m3/hour.

Transmit 03 03 00 01 00 02 94 29 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk Sum

Receive 03 03 08 45 61 02 00 45 5D A1 F8 D7 88 Meaning Slv. Fn. D.C. The Data … The Data … The Data Chk sum

Result: 45610200 is the 32-bit IEEE hexadecimal representation for 3600.125 (in base units of m3/hour) 455DA1F8 is the 32-bit IEEE hexadecimal representation for 3546.123 m3/hour

Note: When using the single register mode, the number of registers to be read is the same as the number of parameters to be read from the associated block. This happens to be two for ‘Block A’ in this example.

Action 2 of 3: Read four registers starting from MODBUS register 1001 (Values Section, ‘Block B’)

Transmit 03 03 03 E9 00 04 94 5B Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk. sum

Receive 03 03 10 46 18 3C 00 3F 19 0A B1 46 15 Meaning Slv. Fn. D.C. The Data … The Data … The Data … The

Receive F4 00 3E E3 40 94 24 24 Meaning Data … The Data … … Chk. Sum

Result:1st. Volume Flow Total… (Integer + Fraction) 46183C00 is the 32-bit IEEE hexadecimal representation for 9743 (in base units of m3/hour) 3F190AB1 is the 32-bit IEEE hexadecimal representation for 0.59781936 (in base units of m3/hour)

2nd. Volume Flow Total… (Integer + Fraction) 4615F400 is the 32-bit IEEE hexadecimal representation for 9597 (in base units of m3/hour) 3EE34094 is the 32-bit IEEE hexadecimal representation for 0.44385207 (in base units of m3/hour)

Note: Fractional values of a rollover total are always accurate to 8 decimal places irrespective of the selected display format for volume categorised data.

Action 3 of 3: Read 1 register starting from MODBUS register 2001 (Values Section, ‘Block C’)

Transmit 03 03 07 D1 00 01 D4 A5 Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk Sum

Receive 03 83 02 61 31 Meaning Slv. Fn. D.C. Chk sum

Result: Response indicates that there are no parameters listed in ‘Block C’




(1b) Objective: Write new fixed values to the two known parameters listed under ‘Block A’ of High-speed List One

Block A Entry 1

Decimal Value (Before Update)

Decimal Value (After Update)

Block A Entry 2

Decimal Value (Before Update)

Decimal Value (After Update)

IV rate 0 3664 GV rate 0 3712

Abbreviations: “IV” = Indicated Volume, “GV” = Gross Volume

Action 1 of 1: Write values to two registers starting from MODBUS register 1 (Values Section, ‘Block A’)

45650000 is the 32-bit IEEE hexadecimal representation for 3664 45680000 is the 32-bit IEEE hexadecimal representation for 3712

Transmit 03 10 00 01 00 02 08 45 65 00 00 45 68 00

Meaning Slv. Fn. Reg. ID Reg. Cnt. DC The Data … The Data … The

Transmit 00 4C 7E

Meaning Data Chk Sum

Receive 03 10 00 01 00 02 11 EA

Meaning Slv. Fn. Reg. ID Reg. Cnt. Chk Sum

Result: Indicated Volume and Gross Volume rates are updated with new fixed values.

Note: The new parameter values are expected by the slave device to be in base measurement units of m3/hour.To find out the base units for other parameter categories, turn to Chapter 9.

(2a) Objective: Read the location IDs of the first three ‘entry’ configuration parameters of Block B

Block A Entry 1 Loc. ID Block A Entry 2 Loc. ID Block A Entry 3 Loc. ID DBM list 1B ptr 1 2459 DBM list 1B ptr 2 2460 DBM list 1B ptr 3 2461

Action 1 of 1: Read three registers starting from MODBUS register 11001 (Loc. IDs Section, ‘Block B’)

Transmit 03 03 2A F9 00 03 DC 00


Receive 03 03 06 09 9B 09 9C 09 9D 59 1B

Meaning Slv. Fn. D.C. The data … The Data … Chk sum

Result: 099B is the 16-bit hexadecimal representation for 2459 – the database location ID of <”DBM list 1B ptr 1”> 099C is the 16-bit hexadecimal representation for 2460 – the database location ID of <”DBM list 1B ptr 2”> 099D is the 16-bit hexadecimal representation for 2460 – the database location ID of <”DBM list 1B ptr 3”>

Note:

2AF9 (Reg. ID) is the hexadecimal representation for 11001



GUIDED EXAMPLE HIGH-SPEED LIST COMMUNICATIONS

(2b) Objective: Add an entry to ‘High-speed List 1’ via the parameter list of Block C

Action 1 of 1: Write the database location ID of <”Gross std vol rate”> into the database location of <”DBM list1C ptr 1”> (ID: 2509)

09CC is the 16-bit hexadecimal representation for 2508 – the MODBUS address for <”DBM list1C ptr 1”> 029D is the 16-bit hexadecimal representation for 0669 – the database location ID of <”Gross std vol rate”>

Transmit 01 10 09 CC 00 01 02 02 9D EE 55

Meaning Slv. Fn. Reg. ID Reg. Cnt. DC The Data Chk Sum

Receive 01 10 09 CC 00 01 C2 6A


Note: At present, the remote manipulation of a parameter list is achieved through the register map for the 7951 database (at the base slave address). See Chapter 7 for further examples of accessing the database.

(3a) Objective: Read data type and size of a value from all parameters listed in ‘Block A’ of High-speed List One

Action 1 of 1: Read two registers starting from MODBUS register 20001 (Types Section, ‘Block A’)

Transmit 03 03 4E 21 00 02 82 CB


Receive 03 03 04 07 04 07 04 9A B5

Meaning Slv. Fn. D.C. The Data … … Chk Sum

Result: 0704: “07” = 32-bit floating-point data type, “04” = 4 bytes for representing the value

Note: See Table 7b.12 on page 7b.18 when interpreting other codes for the data type and size

(4a) Objective: Read value status from each parameter listed in ‘Block A’ of High-speed List One

Action 1 of 1: Read two registers starting from MODBUS register 30001 (Status Section, ‘Block A’)

Transmit 03 03 75 31 00 02 8E 2A


Receive 03 03 04 00 01 00 00 88 33

Meaning Slv. Fn. D.C. The Data … … Chk Sum

Result:There are four bytes of parameter data returned: 0x0001 and 0x0002 0x0001 = “Set” value status 0x0000 = “Live” value status

Note: For the interpretation of other codes, refer to Table 7b.11 on page 7b.18.




Table 7b.11: Codes for all returned states

Value * State Return

0x0000 Live 0x0001 Set 0x0002 Fail 0x0003 Fallback 0x00FF No state

* All values in this table are hexadecimal numbers

Table 7b.12: Interpreting Data from Type and Size Requests

Database Location Type Size (Bytes) * Type (Code)

Character 2 1 Unsigned 8-bit integer 2 2 Unsigned 16-bit integer 2 3 Signed 16-bit integer 2 4 Unsigned 32-bit integer 4 5 Signed 32-bit integer 4 6 32-bit floating-point number 4 7 64-bit floating-point number 8 8 Character String 22 9 Multiple-choice (List) Option 2 10 Location pointer 2 11 Time and date 16 12

* All values in this column are decimal numbers



WONDERWARE COMPATIBILITY NOTES

7b.3 Using Wonderware’s Modbus I/O Server With High-Speed Lists Background The MODBUS specification glances over the concept of different address ranges containing different data types (and only those types in that range), and therefore using different MODBUS command numbers to manipulate the data. The specification goes on to say that ‘It is perfectly acceptable, and very common, to regard all four tables as overlaying one another, if this is the most natural interpretation on the target machine in question’. While individual manufacturers have mostly banded their data somewhat, but in smaller bands that do not fit this ‘four-table’ approach, Wonderware’s software has stuck to the separate address range method rigidly. For some individual manufacturers it has knowledge of, it has allowed them to specify their own arrangements, and will honour them; without that, you must use absolute addressing, which relies on the different command numbers for different ranges. Because 7951 flow computers only support commands 3 and 16 covering the whole range of 0 – 65535, absolute addressing cannot be used; up until now, none of the other manufacturers’ implementations could be used either.

Now With the flexibility of the new high-speed lists, it is now possible to get most important data by simulating one of the other manufacturers. In the future, Wonderware will support the 7951 directly.

For now, here is how you can read floating-point data types and long integers (totals in their most accurate representation) using Wonderware:

1. Configure the communications parameters on the 7951

<Configure>/<Other parameters>/<Communications><Ports> <Port X>/<Modbus parameters>/<Slave features> “Alarm+L1+L2+Dlog” (recommended) <Port X>/<Modbus parameters>/<Long reg access> “Single register” <Port X>/<Modbus parameters>/<Real precision> “Single precision”

<Configure>/<Other parameters>/<Communications>/<Modbus slave> <High-speed list 1>/<Word order> “Modbus default” <High-speed list 1>/<Layout> “Grouped” (recommended) <High-speed list 1>/<Grouped start address> 7001 (required for compatibility reasons) <High-speed list 2>/<Word order> “Modbus default” <High-speed list 2>/<Layout> “Grouped” (recommended) <High-speed list 2>/<Grouped start address> 15001 (required for compatibility reasons)

With this arrangement floating-point values can be read from ‘high-speed list 1’ and long integers read from ‘high-speed list 2’. If you need to be able to read ‘floats’ and ‘longs’ from the same high-speed list, you will need to choose the “Ungrouped” style of register map and re-organise the start registers for each block section as appropriate. You will not be able to read ‘floats’ and ‘longs’ from within the same block, as they require different address ranges.

2. Configure Wonderware’s Modbus I/O server:

(2a) Configure the “Topic Definition” - choose a name such as “Solar2510L1”.

(2b) Select the MODBUS slave address - the base address + 2 (for high-speed list 1).

(2c) Select “Omni” as the ‘Slave device type” – Omni’s arrangement is the only one currently which can be used with the 7951.

(2d) Repeat for 2a – 2c for ‘High-speed List 2’ (if applicable).

You should now be able to use the I/O server via, for example, In Touch.

16-BITCOMMUNICATIONS

(GOULD LIST)(CHAPTER 7 ADDENDUM C)

Chapter 7C: 16-bit Communications (Gould List) Software Version 2510, Issue 4.30.00 (or higher)

Page 7C.2 7951 2510 (Ch07C/AB)

7C 16-bit Communications (Gould List)

7C.1 Overview Chapter 7C is a guide to the software support for 16-bit only MODBUS protocol communications, which utilises the Gould List in this 7951 menu:

<”Configure”>/<”Other parameters”>/<Communications>/<”MODBus slave”>/<”Gould list”>.

This feature is required when a MODBUS Master 1 is to exchange 16-bit 2 data with one or more 7951 Flow Computers operating as a MODBUS Slaves, where all are attached to the same MODBUS network.

16-bits (Word) 1 Byte 1 Byte 8 bits 8 bits= =

Figure 7c.1: 16-bits

Note: For MODBUS network topologies and terminal connections, refer to main Chapter 7.

7C.1.1 Groundwork

On the 7951 Flow Computer, integer and floating-point values of parameters (locations) are represented by 16-bits, 32-bits or 64-bits, depending on the data type of the value – see Table 7c.1 and Figure 7c.2 (below).

Note: Data representation theory is outside the scope of this guide – refer to a data communications book.

64-bits (4 Words) 16-bits (Word) 16-bits (Word) 16-bits (Word) 16-bits (Word)=

16-bits (Word) 16-bits (Word)32-bits (2 Words) =

Figure 7c.2: 32-bits and 64-bits

16-bit communications is unsuitable for accessing a value that is a character string (11x16-bits) or a value that is a time and date (8x16-bits) – they are therefore not included in Table 7c.1 or this guide.

Table 7c.1: 7951 Data types

Data Type Size Unsigned 8-bit integer 16-bits Unsigned 16-bit integer 16-bits Signed 16-bit integer 16-bits Unsigned 32-bit integer 32-bits Signed 32-bit integer 32-bits 32-bit floating point number * 32-bits 64-bit floating point number * 64-bits Multiple-choice (List) Option 16-bits Location pointer 16-bits* Floating-point number is either single-precision (32-bit) or double-precision (64-bit), depending on serial port option.

1 This MODBUS Master device cannot be a 7951 series Flow Computer. Direct communication of a parameter value between 7951

Flow Computers can be performed using the “Peer-To-Peer” communications feature. 2 16 binary bits e.g. 01010101 01010101

Software Version 2510, Issue 4.30.00 (or higher) Chapter 7C: 16-bit Communications (Gould List)

7951 2510 (Ch07C/AB) Page 7C.3

7C.1.2 7951 16-bit communication features

7951 16-bit communications allows a MODBUS Master to:

Read a 16-bit value – the full value – from a 16-bit parameter (location) – Multiple Register Access.

Read a 16-bit value from any 16-bit segment of a 32-bit or 64-bit parameter (location) – Mult. Reg. Access.

Read a full value from a 32-bit of 64-bit parameter (location) – Single Register Access.

Write 3 a 16-bit value – the full value – to a 16-bit parameter (location) – Multiple Register Access.

Write a 16-bit value to any 16-bit segment of a 32-bit or 64-bit parameter (location) – Mult. Reg. Access.

Write a full value to a 32-bit or 64-bit parameter (location) – Single Register Access.

The ‘16-bit value’ may be scaled (x10, x100 or x1000) before transmission to the MODBUS Master and de-scaled ( 10, 100 or 1000) before being saved to an application parameter (location). This optional feature is explained in Section 7C.1.9.

In addition, serial port parameters for selecting Single or Multiple (Long) Register Access, MODBUS Word Order, Single or Double Precision and Totals format affect 16-bit communications – see Section 7C.1.13 for details of their effect.

7C.1.3 16-bit segments (Gould Registers) when using Multiple Register Access

Figure 7c.3 shows how a 16-bit, 32-bit and 64-bit parameter value is viewed as one or more 16-bit segments. When using Multiple Register Access, each segment is a Gould Register that can be individually read or written if set-up in a Gould List.

16-bits (1 Word) 16-bits (1 Word)

16-bits (1 Word) 16-bits (1 Word) 16-bits (1 Word) 16-bits (1 Word)

Gould Register Gould Register

Gould Register Gould Register Gould Register Gould Register

16-bits (1 Word)

Gould Register

16-bit Parameter(Database Location)



Note: A floating-point number is either single-precision (32-bit) or double-precision (64-bit), depending on the Real Precision option selected for the serial port.

Figure 7c.3: 16-bit segments (Gould Registers) when using Multiple Register Access

It follows then that the Gould Register access for a 32-bit (or 64-bit) parameter is slightly different to accessing a 16-bit parameter.

In Figure 7c.4, a 16-bit value is written, as a full value, to the only 16-bit segment (Gould Register) of a 16-bit parameter. Similarly, a whole value can be read from the same Gould Register.

3 The 7951 will prevent writing to parameters (locations) dedicated to incremental totals, such as the Corrected Volume flow total.


Page 7C.4 7951 2510 (Ch07C/AB)

16-bit value

7951 Flow Computer (MODBUS Slave)MODBUS Master

16-bits (1 Word)

Gould Register


Application

Figure 7c.4: Accessing the full value of a 16-bit parameter in one step

In Figure 7c.5, a 16-bit value is read from the first 16-bit segment (Gould Register) of a 32-bit parameter. A further message (request) is required to read to the second 16-bit segment (Gould Register). With values from both segments retrieved, the full value can be assembled by the MODBUS Master.

The same principle applies to 64-bit parameters, except there are four of the 16-bit segments.

Note:More than one Gould Register can be accessed at the same time if the 7951 Gould List is set-up appropriately.

16-bit value


16-bits (1 Word)

Gould Register


Application

16-bits (1 Word)

Gould Register

16-bit value


16-bits (1 Word)

Gould Register


Application

16-bits (1 Word)

Gould Register

(Read first 16-bit segment)

(Read final 16-bit segment)

Figure 7c.5: Accessing a full value of a 32-bit parameter in two steps

7C.1.4 16-bit segments (Gould Registers) when using Single Register Access

Figure 7c.6 shows how a 16-bit, 32-bit and 64-bit parameter value is viewed as one or more 16-bit segments. When using Single Register Access, all 16-bit segments – the full value – equate to one GouldRegister that can be individually read or written if set-up in a Gould List.

Therefore, reading a Gould Register will retrieve the full value, irrespective of the parameter data type. Similarly, a full value can be written to the Gould Register.

Note: More than one Gould Register can be accessed at the same time if the 7951 Gould List is set-up appropriately.


7951 2510 (Ch07C/AB) Page 7C.5

16-bits (1 Word) 16-bits (1 Word)

16-bits (1 Word) 16-bits (1 Word) 16-bits (1 Word) 16-bits (1 Word)

Gould Register

Gould Register

16-bits (1 Word)

Gould Register




Note: A floating-point number is either single-precision (32-bit) or double-precision (64-bit), depending on the Real Precision option selected for the serial port.

Figure 7c.6: 16-bit segments (Gould Registers) when using Single Register Access


Page 7C.6 7951 2510 (Ch07C/AB)

7C.1.5 Gould List

On the 7951 Flow Computer, the Gould List comprises menu entries for nominating up to 50 Gould Registers. Each list entry requires user-entered details, which include:

a user-nominated address for the Gould Register (e.g. 40001) the unique 4-digit location identification number of the associated parameter (e.g. Loc ID: 0144) Word Offset – 0, 1, 2 or 3 – for selecting a 16-bit segment of the parameter value (if applicable) Scaling factor – x10, x100, x1000 or none – for scaling/de-scaling the 16-bit data being exchanged

The 7951 Gould List can be set-up for Multiple Register Access or Single Register (or a mixture if using more than one serial port.)

Figure 7c.7 shows an example 7951 Gould List set-up for Multiple Register Access. There are 3 entries populated with user-entered details.

Gould List entries 1 and 2 are set-up for accessing the first 16-bit segment (Gould Register 40001) and final 16-bit segment (Gould Register 40002) of a 32-bit parameter (location), perhaps a flow rate.

Since the full value of parameter 0144 is represented in 32-bits, the Word Offset option must be used to select which 16-bit segment is associated with the nominated Gould Register address.

Word Offset 0 selects first 16-bit segment. Word Offset 1 selects the final 16-bit segment. (Word Offset 2and 3 are applicable only for a 64-bit parameter.)

Gould List entry 3 is set-up for accessing a 16-bit parameter, but there is a deliberate mistake. The Word Offset is 1, which is incorrect since there is no second 16-bit segment in a 16-bit parameter. Likewise, Word Offsets 2 and 3 would also be incorrect as there are no third and fourth segments. To correct the error, Word Offset 0 must be selected.

Gould List entry 50 is not in use and shows the factory default settings. Note: A location ID of 0 (“Off”) will terminate the 7951 Gould List – do not skip entries in the 7951 Gould List.

Location ID: 0144

459.21Value

Data Size 32-bit

GO

ULD

LIS

T

7951 Flow Computer(MODBUS Slave)

DA

TABA

SE

1

2

3

50

GOULD LIST DATABASE

Location ID:

Scaling:

Gould Reg: 40001

0144

Word Offset: 0

No scaling

Location ID:

Scaling:

Gould Reg: 40002

0144

Word Offset: 1

No scaling

Location ID:

Scaling:

Gould Reg: 50001

1429

Word Offset: 1

No scaling Location ID: 1429

0Value

Data Size 16-bit

Location ID:

Scaling:

Gould Reg: 0

Off

Word Offset: 0

No scaling

Note: A floating-point number (e.g. 459.21) is either single-precision (32-bit) or double-precision (64-bit), depending on the Real Precision option selected for the serial port.

Figure 7c.7: 7951 Gould List (Multiple Register Access)


7951 2510 (Ch07C/AB) Page 7C.7

Figure 7c.8 shows an example 7951 Gould List set-up for Single Register Access. Again, there are 3entries populated with user-entered details.

Gould List entry 1 is set-up for accessing the full value – all 16-bit segments – of Gould Register 40001.

Since the full value of parameter 0144 is read in one go, the Word Offset option is not used and it is kept set to the factory default of Word Offset 0.

Gould List entry 2 is set-up for accessing the full value – all 16-bit segments – of Gould Register 40002.

Again, since the full value of parameter 0167 is read in one go, the Word Offset option is not used and it is kept set to the factory default of Word Offset 0.

Since Gould Register 40001 and 40002 have addresses in sequence and are in consecutive entries, they can both be read at the same time.

Gould List entry 3 is set-up for accessing the full value – a single 16-bit segment – of Gould Register 50001. Again, the Word Offset option is not used and it is kept set to the factory default of Word Offset 0.

Gould Register 40002 and 50001 are in consecutive entries but the addresses are not in sequence; they cannot both be read at the same time.

Gould List entry 50 is not in use and shows the factory defaults.

Note: A location ID of 0 (“Off”) will terminate the 7951 Gould List – do not skip entries in the 7951 Gould List.

Location ID: 0144

459.21Value

Data Size 32-bit

GO

ULD

LIS

T

7951 Flow Computer(MODBUS Slave)

DA

TABA

SE

1

2

3

50

GOULD LIST DATABASE

Location ID:

Scaling:

Gould Reg: 40001

0144

Word Offset: 0

No scaling

Location ID:

Scaling:

Gould Reg: 40002

0167

Word Offset: 0

No scaling

Location ID:

Scaling:

Gould Reg: 50001

1429

Word Offset: 0

No scaling

Location ID: 1429

0Value

Data Size 16-bitLocation ID:

Scaling:

Gould Reg: 0

Off

Word Offset: 0

No scaling

Location ID: 0167

2359.54Value

Data Size 32-bit

Note: A floating-point number (e.g. 459.21) is either single-precision (32-bit) or double-precision (64-bit), depending on the Real Precision option selected for the serial port.

Figure 7c.8: 7951 Gould List (Single Register Access)


Page 7C.8 7951 2510 (Ch07C/AB)

7C.1.6 Gould List: Gould Register Addressing

The address of a Gould Register can be edited to be any number in the range 0 to 65535 (0x0000 to 0xFFFF), as long as it is unique in the Gould List.

Attempts to enter an address outside this range will be responded to with an “** ERROR **” message, on-screen for a few seconds, and the original setting is then restored.

When accessing more than one Gould Register at a time, the user-entered addresses must be in sequence(e.g. 1300, 1301, etc) and in consecutive entries in the Gould List.

When accessing one Gould Register at a time, the addresses of consecutive entries in the Gould List do nothave to be in sequence (e.g. 1300, 1400, etc.)

7C.1.7 Gould List: Parameters (Locations)

To find the unique identification number of a parameter (location), navigate to the parameter screen and press the a-button to display the number.

7C.1.8 Gould List: Word Offset

Word Offset settings in the Gould List are only applicable when using Multiple Register Access (rather than using Single Register Access).

With Multiple Register Access, each Gould Register equates to a 16-bit segment of data. Therefore, you select the segment that will equate to the register.

Word Offset 0The Gould Register is mapped to the only 16-bit segment of a 16-bit parameter value or it is mapped to the first 16-bit segment of a 32-bit or 64-bit parameter value.

Word Offset 1The Gould Register is mapped to the second 16-bit segment of a 32-bit or 64-bit parameter value.

Word Offset 2 The Gould Register is mapped to the third 16-bit segment of a 64-bit parameter value.

Word Offset 3The Gould Register is mapped to the fourth 16-bit segment of a 64-bit parameter value.

Examples can be found in Section 7C.3.

Note: With Single Register Access, each Gould Register equates to the whole value (all 16-bit segments).

7C.1.9 Gould List: Scaling Factor

The scaling factor, 10, 100 or 1000, is effective only when accessing floating-point values.

If selected for a Gould Register, the factor is applied, therefore converting it into a whole number (integer) before or transmitted or vice versa if being saved.

If no scaling factor is to be applied, select “No Scaling” – this is the factory default for each Gould List entry.

The purpose of this feature is for systems that cannot handle float conversions – they may ask for temperature x 100 (as an integer). You cannot get scaled values as a floating-point value.

Practical examples can be found in Section 7C.3.


7951 2510 (Ch07C/AB) Page 7C.9

7C.1.10 MODBUS Message Exchanges

The MODBUS Master can access more than one Gould Registers in one request.

To access the registers, it must transmit a read or write MODBUS protocol message addressed to the 7951 MODBUS slave. The slave will then reply with a MODBUS protocol message.

Note: Write messages can be broadcast to all 7951 MODBUS slaves with a MODBUS slave address of 0.

Gould registers can be accessed through any serial port configured to be a MODBUS slave and the Gould List access is enabled by the port MODBUS feature parameter. (Full configuration details are in Section 7C.2.)

7C.1.11 Read Message Format (Single or Multiple Gould Register Access)

Figure 7c.9 shows the MODBUS function 03 command format. Practical examples, showing other Read messages and responses, can found in Section 7C.3.

Slave Address

Function G. Reg. (H.O.)

G. Reg. (L.O.)

# Of Reg. (H.O.)

# Of Reg. (L.O.)

EC LRC

06 03 9C 41 00 02 X X

Figure 7c.9: MODBUS message for reading from Gould Registers 40001 and 40002

Slave Address – On the 7951, this is a Virtual Slave address: Base Slave Address +5 (= 06 if factory default)

Function – 03 (0x03) is the function code for MODBUS read messages.

G. Reg. – Address of Gould Register, e.g. 40001 (Decimal) or 0x9C41 (Hexadecimal)

# of Reg. – Specify number of Gould Registers to be read, e.g. 0002 (Decimal and Hexadecimal)

EC – Error check number, generated is accordance with the MODBUS specification

LRC – Longitudinal redundancy check number, generated in accordance with the MODBUS specification

7C.1.12 Write Message Format (Single or Multiple Gould Register Access)

Figure 7c.10 shows the MODBUS function 16 command format. Practical examples, showing other Write messages and responses, can found in Section 7C.3.

Slave Add.

Funct. G. Reg. (H.O.)

G. Reg. (L.O.)

Quantity Byte Count

16-bit data 16-bit data EC LRC

06 10 9C 41 00 02 04 (H.O.) (L.O.) (H.O.) (L.O.) X X

Figure 7c.10: MODBUS message for writing to Gould Registers 40001 and 40002

Slave Address – On the 7951, this is a Virtual Slave address: Base Slave Address +5 (= 06 if factory default)

Function – 16 (0x10) is the function code for MODBUS write messages.

Gould Register – Address of Gould Register, e.g. 40001 (Decimal) or 0x9C41 (Hexadecimal)

Quantity – Specify number of Gould Registers to be write to, e.g. 2 for 40001 (0x9C41) and 40002 (0x9C42)

Byte Count – Specify number of bytes of data e.g. 0x02 for a 16-bit value, 0x04 for two 16-bit values, etc.

16-bit data – Up to fifty 16-bit IEEE values, dependent on Quantity field

EC – Error check number, generated is accordance with the MODBUS specification

LRC – Longitudinal redundancy check number, generated in accordance with the MODBUS specification


Page 7C.10 7951 2510 (Ch07C/AB)

7C.1.13 Serial port parameters (locations)

Each serial port has parameters for selecting Single or Multiple (Long) Register Access, MODBUS Word Order, Single or Double Precision and Totals format affect 16-bit communications.

<Long Register Access>The 7951 Flow Computer has support for both Single Register Access and Multiple Register Access. Each serial port is configured to allow one type of register access.

Multiple Register Access:With this type of access, each Gould Register equates to a single 16-bit segment. Therefore, to read a 32-bit value, two Gould Registers are required. Similarly, to read a 64-bit value, four Gould Registers are required.

Single Register Access:With this type of access, each Gould Register equates to all the 16-bit segments required for a full value. Therefore, to read a 16-bit value, 32-bit value or 64-bit value, only one Gould Register is required.

<MODBUS Word Order>The 7951 Flow Computer provides the facility to choose the Word (double-byte) ordering of data fields in MODBUS messages. This feature is individually selectable for each serial port.

Figure 7c.11 shows the effect of the Default Order option and Word Swap option for single-precision (32-bit) and double-precision (64-bit) values. For 64-bit values, the second double Word is the most significant.

WORD '1'(16 Bits)


Word Swap

42 C2 3F 0D

WORD '1'(16 Bits)

WORD '2'(16 Bits)

42 C23F 0D

SINGLE PRECISION

WORD '1'(16 Bits)


Word Swap

40 58 47 E1

WORD '3'(16 Bits)

WORD '4'(16 Bits)

9B 90EA 9E

DOUBLE PRECISION

WORD '3'(16 Bits)

WORD '4'(16 Bits)

9B 90 EA 9E

WORD '2'(16 Bits)

WORD '1'(16 Bits)

47 E1 40 58

Figure 7c.11: Word Ordering Examples

<Real Precision>

Floating-point values (e.g. flow rates) are made available as a 32-bit IEEE (single-precision) number or as a 64-bit IEEE (double-precision) number. The precision level is individually selectable for each serial port.

<Total Format>Each incremental total can be read as two separate 32-bit integers or as a single floating-point value, depending on the option selected. The format is individually selectable for each serial port.

When a flow total value (e.g. 2983.54) is to be read as a 32-bit integer, there is one parameter (location) with the “2953” and another parameter (location) with the “54”.

When a flow total value (e.g. 2983.54) is to be read as a floating-point value, there is just one parameter (location) with the “2953.54”.


7951 2510 (Ch07C/AB) Page 7C.11

7C.2 Configuring and Activation Instructions Follow these instructions to configure and activate 16-bit communications on the 7951 Flow Computer:

1. Ensure that 7951 Flow Computers and MODBUS Maste device are already interconnected to form a MODBUS network. (Guidance on the necessary RS-232 or RS-485 wiring 4 is in the main Chapter 7.)

2. Program a 7951 Flow Computer to be the MODBUS slave device

(2a) Navigate to this menu: <”Configure”>/<”Other Parameters”>/<”Communications”>/<”Ports”>

(2b) Select a Serial Port menu, as appropriate for the serial port connected to the MODBUS network.

(2c) Configure the basic communication parameters for that serial port, as shown in Table 7c.2. (Some localised menu navigation is required to find the parameter screen.)

3. Configure entries in the Gould List

(3a) Navigate to this menu: <”Configure”>/<”Other Parameters”>/<”Communications”>/<”MODBus slave”>

(3b) Select this menu: <“Gould list”>

(3c) Configure each list entry, as guided in Table 7c.3. Start with configuring Entry 1, then configure Entry 2, and so forth. Avoid skipping an entry, since the list is terminated by a location ID of 0.


The MODBUS Master can read and write to the Gould Registers.

4 To avoid the risk of flow computer restarts, it is advisable to pre-set the signalling standard – RS-232 or RS-485 – for 7951 serial

ports before establishing the physical connections.


Page 7C.12 7951 2510 (Ch07C/AB)

Table 7c.2: Basic Serial Port Communication Parameters

Parameter * (Database Location) Instructions and Comments Factory Default

Setting

Comms port owner Select the multiple-choice option with “Modbus slave”. “MODBUS slave”

Port Baud rate Select a rate that will be the same for the MODBUS Master device and all 7951 MODBUS slave devices. “19200”

Port char format Select a character transmission format (as agreed for the MODBUS network). If unsure, keep the factory default. “8 bits none 1 stop”

Port handshaking Select either “None” or “XonXoff” unless the cable supports “CTS/RTS”. (If unsure, keep the factory default.) “None”

Port RS232 / 485 *** Select signalling standard for the MODBUS network ** “RS 232”

Port Modbus mode Select the option that is compatible with the other MODBUS network devices. (If unsure, keep the factory default.) “RTU”

P Modbus word order Select an option that is compatible with the Master device. (If unsure, keep the factory default.) “Modbus default”

P MODB slave add Edit the Base Slave Address of this slave. 1

P Modbus features Select the multiple-choice option that includes “Gou“ (Gould) “None”

P long reg access Choose single or multiple Gould Register access. “Multiple registers”

P MODB total format Select how total values are to be transmitted – either 32-bit integers or as a single/double-precision floating-point value. “32-bit integer”

P MODB precision Select the accuracy of all floating-point values for this serial port: single-precision (32-bits) or double-precision (64-bits). “Single”

* The on-screen parameter descriptor includes a digit to identify the associated serial port. ** A 7951 may perform ‘warm restarts’ if it is configured to be “RS 232” when it should be “RS 485”.

*** Parameter is not applicable to Serial Port One since it is for RS-232 devices only. Abbreviations used: “P” = Port, “reg” = register, “addr” = address, “char” = character, “MODB” = MODBUS

Table 7c.3: Gould List Entry Parameters (Locations)


Setting

List1 Gould reg Enter a numeric address for the Gould Register e.g. 40001. 0

List1 mapped loc ** Enter the unique identification number (Loc ID) of the parameter (location) to be mapped to the Gould Register. Off

List1 Word Offset If using multiple register access and mapped parameter has a 32-bit/64-bit value, select the 16-bit segment of the value to be accessed.

“Word Offset 0”

List1 scale factor If the 16-bit data is a floating-point number, it can be scaled into an integer (x10, x100 or x1000) just before transmission to the MODBUS Master. Similarly, it can be de-scaled before saving it.

“No scaling”

* The on-screen parameter descriptor includes a number to identify the list entry. ** Entering a valid location number will immediately result in the number changing to the parameter descriptor. Editing

a location number for a parameter that does not exist is responded to with a “** ERROR **” message appearing briefly, and the original setting is then restored.

Abbreviation used: “reg” = register, “loc” = location


7951 2510 (Ch07C/AB) Page 7C.13

7C.3 Guided Examples This section is a practical guide to accessing Gould Registers of a 7951 MODBUS Slave through the Gould List feature.

What to do here:

1. Ensure that the 7951 Flow Computer is suitably configured as guided in Section 7C.2.

2. Follow examples from Table 7c.4 or Table 7c.5.

In the examples, MODBUS message sequences aim to show the how to read from Gould Registers and write to Gould Registers. Every example features an objective, an action and a result

Objective(s) For an example, the objective could be to read a 16-bit parameter value.

Action(s) Actions consist of one or more MODBUS protocol commands. They are represented in this documentation as tabulated hexadecimal values in sequence for transmission by the Master device.

Expected responses from the 7951 MODBUS slave device are also shown as tabulated values. Table 7c.6 is a list of all the abbreviations of meanings that can appear with a sequence. Use them to distinguish the important elements of the message.

Result This is a brief analysis of the MODBUS slave response to an action. Note: Values are communicated in base units, which may not be the same as the displayed units – see Table 7c.7.

3. Experiment

Try out the examples and then adapt them to suit your requirements.

Table 7c.4 : Summary of examples (reading from Gould Registers)

ExampleNumber

Totalsformat

PrecisionWordOrder

RegisterAccess

ScalingAccess

Beyond Value Consecutive

RegistersPage

1 X Single Default Multiple None No Yes 15

2 X Single Default Multiple None No No 16

3 X Single Default Multiple None Yes Yes 17

4 X Single Default Multiple x100 No Yes 18

5 X Single Default Single None No Yes 19

6 X Double Default Multiple None No Yes 20

7 X Double Default Single None No Yes 21

8 Integer Single Default Single None No Yes 22

9 Integer Single Default Multiple None No Yes 23

10 Fl. point Double Default Single None No Yes 24


Page 7C.14 7951 2510 (Ch07C/AB)

Table 7c.5: Summary of examples (writing to Grould Registers)

ExampleNumber

Totalsformat Precision Word

OrderRegisterAccess Scaling Access


Registers Page



3 X Single Default Single None No Yes 27

4 X Single Default Multiple x100 No Yes 28

5 X Single Default Single x100 No Yes 29

Table 7c.6: Abbreviations for Interpreting Elements of Transmit and Response Sequences

Abbreviation Meaning

Slv. Base Slave Address +5. It is 0x06 for the examples. Err. Error code. E.g. 83 = Error reading / Exception Fn. Function code. E.g. 03 = Read Gould Register(s)

Reg. Cnt Quantity of Gould Registers Reg. ID Gould Register number

D.C. Number of ‘data bytes’ in reply Data Data byte

EC & LRC Calculated checksum, which is two bytes at the end

Table 7c.7: Base units of measurement

Category Base units Temperature Deg. C

Pressure bar absDifferential pressure mbar

Density kg/m3

Frequency sFraction

Time seconds Flow factor pulse/m3

Volume total m3

Base volume total std m3

Mass Total kg Energy Total MJ

Mass rate g/minVolume rate m3/hourEnergy rate MJ/hour

Energy value (mass) MJ/kg Energy value (volume) MJ/m3

Base volume rate Std m3/hour Length m

Dynamic viscosity cP Absolute zero Deg.C

Velocity m/s Orifice Coeffient PPM/Deg.C


7951 2510 (Ch07C/AB) Page 7C.15

7C.3.1 Gould List Read Access: Example 1

Objective:Read Meter-run Temperature parameter (database location ID: 0666) which has a 32-bit (single-precision) floating-point value.

Totalsformat

PrecisionWordOrder

RegisterAccess

ScalingAccess


RegistersX Single Default Multiple None No Yes

This example involves reading two Gould Registers 1300 and 1301; this is to get the two lots of 16-bit data. Importantly, they are given consecutive entries in the Gould List.

Serial Port ConfigurationModbus default Word order, MODBUS (Base) Slave Address = 1, multiple register access, single-precision.

Gould List Configuration

Gould List Entry 1: <List1 Gould reg 1> = 1300 <List1 mapped loc 1> = 0666 (Meter temperature) <List1 WordOffset 1> = “Word offset 0” <List1 scale fact 1> = “No scaling”


ActionRead Gould Registers 1300 and 1301

Transmit 06 03 05 14 00 02 85 74

Meaning Slv. Fn. Reg. ID Reg. Cnt. EC LRC

Response 06 03 04 42 0C 00 00 58 88

Meaning Slv. Fn. D.C. Data Data Data Data EC LRC

Result420C0000 is the 32-bit IEEE hexadecimal representation for 35.0 (in base units of C)420C is the 16-bit data from Gould Register 1300 and 0000 is the 16-bit data from Gould Register 1301


Page 7C.16 7951 2510 (Ch07C/AB)


Note: This is an error response example, which is a variation of Example 1.


Totalsformat

PrecisionWordOrder

RegisterAccess

ScalingAccess


RegistersX Single Default Multiple None No No

This is similar to example 1, except Gould Registers 1300 and 1301 are not given consecutive entries in the Gould List. Subsequently, there is an error response transmitted by the 7951 Flow Computer.

Serial Port ConfigurationModbus default Word order, MODBUS (Base) Slave Address = 1, Multiple Register Access, Single-precision.



Gould List Entry 2: <List1 Gould reg 2> = 40001 <List1 mapped loc 2> = 0144 (Corrected volume flow rate) <List1 WordOffset 2> = “Word offset 0” <List1 scale fact 2> = “No scaling”



Transmit 06 03 05 14 00 02 85 74


Response 06 83 02 71 30

Meaning Slv. Fn. D.C. Chk sum

Result An error reponse (code 83) is given since Gould Registers 1300 and 1301 are not given consecutive entries in the Gould List.


7951 2510 (Ch07C/AB) Page 7C.17


Note: This is an error response example, which is a variation of Example 1.


Totalsformat

PrecisionWordOrder

RegisterAccess

ScalingAccess


RegistersX Single Default Multiple None Yes Yes

This is similar to Example 1, except there is an attempt to read beyond Gould Register 1300 and 1301 by using the Word Offset 2 option and Word Offset 3 option.

Subsequently, there is an error response transmitted by the 7951 Flow Computer, since the parameter does not have a 64-bit (double-precision) floating-point value.






Transmit 06 03 05 14 00 02 85 74


Response 06 83 02 71 30

Meaning Slv. Fn. D.C. EC LRC

Result An error response (code 83) is given since parameter does not have a 64-bit (double-precision)

floating-point value.


Page 7C.18 7951 2510 (Ch07C/AB)



Totalsformat

PrecisionWordOrder

RegisterAccess

ScalingAccess


RegistersX Single Default Multiple Yes No Yes

This example, which is a variation of Example 1, involves reading scaled (x100) values from two Gould Registers 1300 and 1301.



Gould List Entry 1: <List1 Gould reg 1> = 1300 <List1 mapped loc 1> = 0666 (Meter temperature) <List1 WordOffset 1> = “Word offset 0” <List1 scale fact 1> = “Int (value x 100)”

Gould List Entry 2: <List1 Gould reg 2> = 1301 <List1 mapped loc 2> = 0666 (Meter temperature) <List1 WordOffset 2> = “Word offset 1” <List1 scale fact 2> = “Int (value x 100)”


Transmit 06 03 05 14 00 02 85 74


Response 06 03 04 00 00 0D AC 88 1E

Meaning Slv. Fn. D.C. Data Data Data Data EC LRC

Result00000DAC is the 32-bit IEEE hexadecimal representation for 3500.0 (in base units of C)


7951 2510 (Ch07C/AB) Page 7C.19


Objectives: Read Meter-run Temperature (Loc. ID: 0666), a 32-bit (single-precision) floating-point value.

Read Meter-run Temperature (Loc. ID: 0666) and Corrected Volume Rate (loc. ID: 0144), which both have 32-bit (single-precision) floating-point values.




RegistersX Single Default Single None No Yes

Importantly, and unlike previous examples, single register access is used – only one Gould Register is required to get the full value (all 16-bit segments). Therefore, the Word Offset option has no effect.

This example involves: Reading the whole temperature value from a single Gould Register – Action 1 Reading whole values of temperature and flow rate from two consecutive Gould Registers – Action 2

Serial Port ConfigurationModbus default Word order, MODBUS (Base) Slave Address = 1, single register access, single-precision.


Gould List Entry 1: <List1 Gould reg 1> = 1305 <List1 mapped loc 1> = 0666 (Meter temperature) <List1 scale fact 1> = “No scaling”


Action 1Read whole temperature value from Gould Register 1305

Transmit 06 03 05 19 00 01 54 B6 Meaning Slv. Fn. Reg. ID Reg. Cnt. EC LRC

Response 06 03 04 42 0C 00 00 58 88 Meaning Slv. Fn. DC Data Data Data Data EC LRC

Result The data, 420C0000, is the 32-bit IEEE hexadecimal representation for 35.0 (in base units of C)420C is the first 16-bit segment of data read from Gould Register 1305 (i.e. the integer part, 35) 0000 is the final 16-bit segment of data read from Gould Register 1305 (i.e. the fractional part, .0)

Action 2Read Gould Registers 1305 and 1306

Transmit 06 03 05 19 00 02 54 B6 Meaning Slv. Fn. Reg. ID Reg. Cnt. EC LRC

Response 06 03 04 42 0C 00 00 42 20 00 00 D3 F8 Meaning Slv. Fn. DC Data Data Data Data Data Data Data Data EC LRC

Result The data, 420C0000, is the IEEE hexadecimal representation for 35.0 (in base units of C)420C is the first 16-bit segment of data read from Gould Register 1305 (i.e. the integer part. 35); the 0000 that follows final 16-bit segment of data read from Gould Register 1305 (i.e. the fractional part, .0)

The data, 42200000, is the IEEE hexadecimal representation for 40.0 (in base units of m3/hour)4220 is the first 16-bit segment of data read from Gould Register 1306; the 0000 is the other segment


Page 7C.20 7951 2510 (Ch07C/AB)


Objective:Read Meter-run Temperature parameter (Loc. ID: 0666) which has a 64-bit (double-precision) floating-point value.

Totalsformat

PrecisionWordOrder

RegisterAccess

ScalingAccess


RegistersX Double Default Multiple None No Yes

This example involves reading four Gould Registers 1300 - 1303; this is to get four lots of 16-bit data. Importantly, they are given consecutive entries in the Gould List.

Serial Port ConfigurationModbus default Word order, MODBUS (Base) Slave Address = 1, multiple register access and double-precision.







Transmit 06 03 05 14 00 04


Response 06 03 08 40 41 80 00 00 00 00 00

Meaning Slv. Fn. D.C. Data Data Data Data Data Data Data Data EC LRC

Result404180000000 is the 64-bit IEEE hexadecimal representation for 35.0 (in base units of C)4041 is the 16-bit data from Gould Register 1300, 8000 is the 16-bit data from Gould Register 1301, and so forth.


7951 2510 (Ch07C/AB) Page 7C.21


Objectives: Read Meter-run Temperature (Loc. ID: 0666), a 64-bit (double-precision) floating-point value.

Read Meter-run Temperature (Loc. ID: 0666) and Corrected Volume Rate (loc. ID: 0144), which both have 64-bit (double-precision) floating-point values.




RegistersX Double Default Single None No Yes

Importantly for this example, single register access is used – only one Gould Register is required to get a fullvalue (i.e. all four 16-bit segments). Therefore, the Word Offset option has no effect.

This example involves: Reading the whole temperature value from one Gould Register – Action 1 Reading whole values of temperature and flow rate from two consecutive Gould Registers – Action 2

Serial Port ConfigurationModbus default Word order, MODBUS (Base) Slave Address = 1, single register access, double-precision.



Gould List Entry 2: <List1 Gould reg 2> = 1306 <List1 mapped loc 2> = 0144 (Corrected Volume flow rate) <List1 scale fact 2> = “No scaling”

Action 1: Read whole temperature value from Gould Register 1305Transmit 06 03 05 19 00 01 54 B6 Meaning Slv. Fn. Reg. ID Reg. Cnt. EC LRC

Response 06 03 08 40 41 80 00 00 00 00 00 C5 57 Meaning Slv. Fn. DC Data Data Data Data Data Data Data Data EC LRC

Result4041 8000 0000 0000 is the 64-bit IEEE hexadecimal representation for 35.0 (in base units of C)

The first 8 bytes of data, 4041 8000, is the first and second 16-bit data segments (of the 64-bit value) read from Gould Register 1305 (i.e. the integer part, 35)

The last 8 bytes of data, 0000 0000, is the third and fourth 16-bit data segments (of the 64-bit value) read from Gould Register 1305 (i.e. the fractional part, .0)

Action 2: Read Gould Registers 1305 and 1306Transmit 06 03 05 19 00 02 14 B7 Meaning Slv. Fn. Reg. ID Reg. Cnt. EC LRC

Response 06 03 10 40 41 80 00 00 00 00 00 40 44Meaning Slv. Fn. DC Data Data Data Data Data Data Data Data Data Data

Response 00 00 00 00 00 00 60 99 Meaning Data Data Data Data Data Data EC LRC

Result4041 8000 0000 0000, is the 64-bit IEEE hexadecimal representation for 35.0 (in base units of C)4042 0000 0000 0000, is the 64-bit IEEE hexadecimal representation for 40.0 (in base units of m3/hour)


Page 7C.22 7951 2510 (Ch07C/AB)


Objectives: Read Indicated Volume total in 32-bit integer format.

Totalsformat

PrecisionWordOrder

RegisterAccess

ScalingAccess


RegistersInteger X Default Multiple None No Yes

Importantly for this example, Multiple Register Access is used – more than one Gould Register is required to get a full 32-bit value (i.e. all 16-bit data segments). Therefore, the Word Offset option is required.

This example involves reading two whole integer values, requiring four Gould Registers.

Serial Port ConfigurationModbus default Word order, MODBUS (Base) Slave Address = 1 and Multiple Register Access.


Gould List Entry 1: <List1 Gould reg 1> = 1400 <List1 mapped loc 1> = 0174 (Indicated Volume total, whole part) *<List1 WordOffset 1> = “Word Offset 0” <List1 scale fact 1> = “No scaling”

Gould List Entry 2: <List1 Gould reg 2> = 1401 <List1 mapped loc 2> = 0174 (Indicated Volume total, whole part) *<List1 WordOffset 2> = “Word Offset 1” <List1 scale fact 2> = “No scaling”

Gould List Entry 3: <List1 Gould reg 3> = 1402 <List1 mapped loc 3> = 0172 (Indicated Volume total, fractional part) *<List1 WordOffset 3> = “Word Offset 0” <List1 scale fact 3> = “No scaling”

Gould List Entry 4: <List1 Gould reg 4> = 1403 <List1 mapped loc 4> = 0172 (Indicated Volume total, fractional part) *<List1 WordOffset 4> = “Word Offset 1” <List1 scale fact 4> = “No scaling”

* Parameter is not visible within the menu system. For a full location listing, contact factory.

Action 1: Read Gould Registers 1400 - 1403

Transmit 06 03 05 78 00 04 C5 6B


Response 06 03 10 45 09 A0 00 3F 7D 0B 5C 51 09

Meaning Slv. Fn. DC Data Data Data Data Data Data Data Data EC LRC

Result4509 A000 is the 32-bit IEEE hexadecimal representation for 2202.0 (in base units of m3)

The first 8 bytes of data, 4509 A000, is the first and second 16-bit data segments (of the 32-bit value) read from Gould Register 1400 (i.e. the integer part, 2202.0) 3F7D 0B5C is the 32-bit IEEE hexadecimal representation for 0.98845457 (in base units of m3)

The last 8 bytes of data, 3F7D 0B5C, is the first and second 16-bit data segments (of the 32-bit value) read from Gould Register 1401 (i.e. the fractional part, 0.98845457)

Note: Fractional values of a rollover total are always accurate to 8 decimal places irrespective of the selected display format for volumetric values.


7951 2510 (Ch07C/AB) Page 7C.23


Objectives: Read Indicated Volume total in 32-bit integer format.

Totalsformat

PrecisionWordOrder

RegisterAccess

ScalingAccess


RegistersInteger X Default Single None No Yes

Importantly, single register access is used – only one Gould Register is required to get a full value (i.e. all 16-bit data segments). Therefore, the Word Offset option has no effect.

This example involves reading two whole integer values from two Gould Registers.

Serial Port ConfigurationModbus default Word order, MODBUS (Base) Slave Address = 1 and Single Register Access.


Gould List Entry 1: <List1 Gould reg 1> = 1400 <List1 mapped loc 1> = 0174 (Indicated Volume total, whole part) *<List1 scale fact 1> = “No scaling”

Gould List Entry 2: <List1 Gould reg 2> = 1401 <List1 mapped loc 2> = 0172 (Indicated Volume total, fractional part) *<List1 scale fact 2> = “No scaling”

* Parameter is not visible within the menu system. For a full location listing, contact factory.

Action 1: Read whole value from Gould Registers 1400 and 1401 Transmit 06 03 05 78 00 02 45 69


Response 06 03 08 45 09 A0 00 3F 7D 0B 5C 51 09


Result4509 A000 is the 32-bit IEEE hexadecimal representation for 2202.0 (in base units of m3)

The first 8 bytes of data, 4509 A000, is the first and second 16-bit data segments (of the 32-bit value) read from Gould Register 1400 (i.e. the integer part, 2202.0) 3F7D 0B5C is the 32-bit IEEE hexadecimal representation for 0.98845457 (in base units of m3)

The last 8 bytes of data, 3F7D 0B5C, is the first and second 16-bit data segments (of the 32-bit value) read from Gould Register 1401 (i.e. the fractional part, 0.98845457)

Note:Fractional values of a rollover total are always accurate to 8 decimal places irrespective of the selected display format for the value.


Page 7C.24 7951 2510 (Ch07C/AB)


Objectives: Read Indicated Volume total (Loc. ID: 0167) as a 64-bit (double-precision) floating-point value.

Totalsformat

PrecisionWordOrder

RegisterAccess

ScalingAccess


RegistersFl. Point Double Default Single None No Yes

Importantly, single register access is used – only one Gould Register is required to get a full value (i.e. all four 16-bit segments). Therefore, the Word Offset option has no effect.

This example involves reading the whole double-precision value from one Gould Register.

Serial Port ConfigurationModbus default Word order, MODBUS (Base) Slave Address = 1, single register access, double-precision.


Gould List Entry 1: <List1 Gould reg 1> = 1400 <List1 mapped loc 1> = 0167 (Indicated Volume total) <List1 scale fact 1> = “No scaling”

Action 1: Read whole value from Gould Register 1400

Transmit 06 03 05 78 00 01 05 68


Response 06 03 08 40 A7 4F 14 44 35 79 DD 84 52


Result40A7 4F14 4435 79DD is the 64-bit IEEE hexadecimal representation for 2983.54 (in base units of m3)

The first 8 bytes of data, 40A7 4F14, is the first and second 16-bit data segments (of the 64-bit value) read from Gould Register 1400 (i.e. the integer part, 2983)

The last 8 bytes of data, 4435 79DD, is the third and fourth 16-bit data segments (of the 64-bit value) read from Gould Register 1400 (i.e. the fractional part to 8 decimal places)

Note:Fractional values of a rollover total are always accurate to 8 decimal places irrespective of the selected display format for the value.


7951 2510 (Ch07C/AB) Page 7C.25

7C.3.11 Gould List Write Access: Example 1

Objective:Write 35.5 ( C) to Meter-run Temperature parameter (Loc. ID: 0666) as a 32-bit (single-precision) floating-point value.

Totalsformat

PrecisionWordOrder

RegisterAccess

ScalingAccess



This example involves writing to two consecutive Gould Registers 1300 and 1301; this is to write two separate 16-bit values (35 and 5). Importantly, they are given consecutive entries in the Gould List.





ActionWrite “35” (420E, IEEE hex.) to Gould Register 1300. Write “5” (0000, IEEE hex.) to Gould Register 1301

Transmit 06 10 05 14 00 02 04 42 0E 00 00 A3 CF

Meaning Slv. Fn. Reg. ID Reg. Cnt. D.C. Data Data Data Data EC LRC

Response 06 10 05 14 00 02 00 B7


Result Echo of Gould Register address field, 1300 (0x0514), and Quantity field, 2 (0x02) indicate success.


Page 7C.26 7951 2510 (Ch07C/AB)


Objectives:1. Write 50.2 ( C) to Meter-run Temperature parameter (Loc. ID: 0666) as a 32-bit (single-precision) value. 2. Write 3600.0 (m3/hour) to Corrected Volume flow rate (Loc. ID: 0144) as a 32-bit (single-precision) value.





This example involves writing to four consecutive Gould Registers 1300 - 1303; this is to write four 16-bit values (50, 2, 3600 and 0). Importantly, they are given consecutive entries in the Gould List.





Gould List Entry 3: <List1 Gould reg 3> = 1302 <List1 mapped loc 3> = 0144 (Corrected Volume flow rate) <List1 WordOffset 3> = “Word offset 0” <List1 scale fact 3> = “No scaling”


ActionWrite “50” (4248 in IEEE) to Gould Register 1300 and “2” (CCCD in IEEE) to Gould Register 1301 Write “360” (43B4 in IEEE) to Gould Register 1302 and “0” (0000 in IEEE) to Gould Register 1303

Transmit 06 10 05 14 00 04 08 42 48 CC CD 43 B4 Meaning Slv. Fn. Reg. ID Reg. Cnt. D.C. Data Data Data Data Data Data

Transmit 00 00 E9 1E Meaning Data Data EC LRC

Response 06 10 05 14 00 04 80 B5 Meaning Slv. Fn. Reg. ID Reg. Cnt. EC LRC



7951 2510 (Ch07C/AB) Page 7C.27


Objectives:1. Write 50.2 ( C) to Meter-run Temperature parameter (Loc. ID: 0666) as a 32-bit (single-precision) value. 2. Write 3600.0 (m3/hour) to Corrected Volume flow rate (Loc. ID: 0144) as a 32-bit (single-precision) value.

Totalsformat

PrecisionWordOrder

RegisterAccess

ScalingAccess


RegistersX Single Default Single None No Yes

This is a variation of Example 2. Importantly, Single Register Access is used – only one Gould Register is required to get a full value (i.e. all 16-bit segments). Therefore, the Word Offset option has no effect.

This example involves writing whole single-precision values to two Gould Registers.

Serial Port ConfigurationModbus default Word order, MODBUS (Base) Slave Address = 1, single register access, single-precision.



Gould List Entry 2: <List1 Gould reg 2> = 1301 <List1 mapped loc 2> = 0144 (Corrected Volume flow rate) <List1 scale fact 2> = “No scaling”

ActionWrite “50.2” (4248CCCD in IEEE) to Gould Register 1300 Write “360.0” (43B40000 in IEEE) to Gould Register 1301

Transmit 06 10 05 14 00 02 08 42 48 CC CD 43 B4

Meaning Slv. Fn. Reg. ID Reg. Cnt. D.C. Data Data Data Data Data Data

Transmit 00 00 09 01

Meaning Data Data EC LRC

Response 06 10 05 14 00 02 00 B7




Page 7C.28 7951 2510 (Ch07C/AB)


Objectives:1. Write 36000.0 (m3/hour) to Corrected Volume flow rate (Loc. ID: 0144) as a 32-bit (single-precision) value.

Totalsformat

PrecisionWordOrder

RegisterAccess

ScalingAccess


RegistersX Single Default Multiple x100 No Yes

Importantly with this example, the 36000.0 is de-scaled to be saved as 360.0. Since Multiple Register Access is to be used, two Gould Registers are required to write the full 32-bit value (i.e. two 16-bit data segments). Therefore, the Word Offset option is required.

This example involves writing whole single-precision values – 36000.0 and 0.0 – to two Gould Registers.

Serial Port ConfigurationModbus default Word order, MODBUS (Base) Slave Address = 1, Multiple Register Access, Single-precision.


Gould List Entry 1: <List1 Gould reg 1> = 1300 <List1 mapped loc 1> = 0144 (Corrected Volume flow rate) <List1 WordOffset 1> = “Word offset 0” <List1 scale fact 1> = “Int (value x 100)”


Actions1. Write “36000.0” (470C in IEEE hexadecimal) to Gould Register 1300 2. Write “0.0” (A000 in IEEE hexadecimal) to Gould Register 1301

Transmit 06 10 05 14 00 02 04 47 0C A0 00 7A C3


Response 06 10 05 14 00 02 00 B7


Result Echo of Gould Register address field, 1300 (0x0514), and Quantity field, 02 (0x02) indicates success.


7951 2510 (Ch07C/AB) Page 7C.29


Objectives:1. Write 36000.0 (m3/hour) to Corrected Volume flow rate (Loc. ID: 0144) as a 32-bit (single-precision) value.

Totalsformat

PrecisionWordOrder

RegisterAccess

ScalingAccess


RegistersX Single Default Single x100 No Yes

Importantly with this example, the 36000.0 is de-scaled to be saved as 360.0. Since Single Register Access is to be used, only one Gould Register is required to write the full 32-bit value (i.e. all 16-bit data segments). Therefore, the Word Offset option is not used.

This example involves writing a whole single-precision value, 36000.0, to a Gould Register.

Serial Port ConfigurationModbus default Word order, MODBUS (Base) Slave Address = 1, Single Register Access, Single-precision.


Gould List Entry 1: <List1 Gould reg 1> = 1300 <List1 mapped loc 1> = 0144 (Corrected Volume flow rate) <List1 scale fact 1> = “Int (value x 100)”

ActionWrite “36000.0” (470C A000 0000 0000 in IEEE) to Gould Register 1300

Transmit 06 10 05 14 00 01 04 47 0C A0 00 7A F0


Response 06 10 05 14 00 01 40 B6


Result Echo of Gould Register address field, 1300 (0x0514), and Quantity field, 0001 (0x01) indicates success.


Page 7C.30 7951 2510 (Ch07C/AB)

‘INTELLIGENTTRANSMITTER’

MONITOR(CHAPTER 7 ADDENDUM D)

Chapter 7D: Intelligent Instrument Monitor Software Version 2510, Issue 4.30.00 (or higher

Page 7D-2 (Ch07D/AB)

7D ‘Intelligent Transmitter’ Monitor

7D.1 Overview Chapter 7D is a guide to accessing process variables and diagnostic data from an ‘intelligent transmitter’. The transmitter must have a communication port that supports RS-485 MODBUS® communications.

Data read or written by the 7951 Flow Computer can be in integer, or floating-point format. When a floating-point value is read, it can be ‘forwarded’ to user-specified target parameter (database location). In addition to this forwarding process, a floating-point value can be automatically re-scaled into alternative units.

The monitoring feature operates with ‘intelligent’ transmitters, such as the Micro Motion® Series 2000 (multivariable) digital transmitter (liquid) and Daniel Senior Sonic™ flow meter (gas).

In the case of the Micro Motion® digital transmitter, it may require some pre-configuring. This is explained in Section 7D.2, along with a step-by-step procedure.

7D.1.1 Transmitter Monitor features Features: Monitor on/off selection switch. Polling method selection. Polling interval selection. Up to 32 registers for accessing 16-bit integer data of transmitter variables (and other data). Up to 16 registers for accessing floating-point data of transmitter variables (and other data). Forwarding of floating-point data to target parameters (database locations) with optional re-scaling. * Support for accessing registers in Message Blocks, as used by Daniel Senior Sonic™ flow meter. Input alarm, “Modb fail slv”, which is raised upon occurrence of communication error or time-out. **

* An Input alarm, “Modb bad target”, is raised if target parameter is not in fixed list of parameters (Table 7d.1, page 7D-4).

** The alarm message includes slave identification number (1-16) and activity (“R” – read failed or “W” – write failed).

7D.1.2 Where is the Transmitter Monitor in the 7951 menu system?

Figure 7d.1 (below) shows how to navigate from the MAIN MENU to the TRANSMITTER MONITOR menu, and includes the keypad strokes needed to arrive at the menu. Apart from configuring parameters in this menu, parameters for a 7951 serial port must also be configured. The menus for this task are located within the COMMUNICATIONS menu. Note: The full setting-up procedure is in Section 7D.3.

Configure

Other parameters

Communications

x3

ax5

a

b

Modbus master c

Transmitter monitor a

Note: Menus illustrated here are for release of software version 2510 at time of publication.

Figure 7d.1: Navigation to the TRANSMITTER MONITOR menu

Software Version 2510, Issue 4.30.00 (or higher) Chapter 7D: Intelligent Instrument Monitor)

(Ch07D/AB) Page 7D-3

7D.1.3 What is in the TRANSMITTER MONITOR menu?

Figure 7d.2 shows a map of the menu, and gives a briefing on the main elements. A more detailed explanation of each element follows the diagram, pages 7D-3 to 7D-6.

Note: The full setting-up procedure is included in Section 7D.3.

Enable/disablePolling

RegistersMessage blocks

Monitor enableDisable

a

Monitor on/off selection screen.

bc

d

Further menus for detailing upto 32 Registers to handlevariables with integer values.

Further menus for detailing up to16 Registers to handle variableswith floating-point values.

TransmitterMonitor menu

a

b

Int registersFloat registers

Poll methodPoll interval

Polling menu leading toscreens for configuring pollmethod and polling interval.

Message block 1Message block 2Message block 3Message block 4

Message blocks menu leading to screensfor detailing up to 32 message blocks.

Message block 29Message block 30Message block 31Message block 32

x7x7


Figure 7d.2: TRANSMITTER MONITOR menu map

Monitor On/OffSwitch options are “Enable” or “Disable”: “Enable” – switches the Monitor on. “Disable” – switches the Monitor off.

Monitor PollingPolling method options are “Optmize” (factory default) or “1 poll/reg”: “Optmize” – monitor will read registers at successive addresses in single poll. “1 poll/reg” – monitor will read a single register at a time, working through listed registers one-by-one.

The factory default setting for the interval between polling is 2.0 seconds. This can be edited to be any period you require in whatever time units are selectable (seconds, minutes, hours, etc). If a value of 0.0 is entered, the polling is constant, but could affect cycle times.



Integer Register List

Each entry in the list comprises parameters to detail as follows:

Value – If “Live”, integer value from transmitter shown. If status is “Set”, value is written to transmitter.

Slave device – Select a MODBUS Slave Device record for the transmitter (see Section 7D.1.4).

Register address – Enter full MODBUS register address of the transmitter variable (e.g. 40392).

Message block – If supported by transmitter, select a Message Block (see page 7D-5 for details).

Byte offset – Applicable only if using Message Block support (see page 7D-5 for details).

Note: Forwarding and re-scaling support is not offered for integer values.

Floating-point Register List

Each entry in the list comprises parameters to detail as follows:

Value – If “Live”, raw value from transmitter shown. If status is “Set”, value is written to transmitter.

Slave device – Select a MODBUS Slave Device record for the transmitter (see Section 7D.1.4).

Register address – Enter the full MODBUS register address of a transmitter variable (e.g. 40392).

Message block – If supported by transmitter, select a Message Block (see page 7D-5 for details).

Byte offset – Applicable only if using Message Block support (see page 7D-5 for details).

Target location – Enter location ID of parameter (Table 7d.1), to which is forwarded the raw/post-scaled value.

Unit – Enter a code from Table 7d.2 to identify units of Value. (If not listed, ignore and use Scale factor).

Scaling factor – If needed, enter a multiplier factor to scale the raw value into base units for forwarding.

Table 7d.1: Allowed target parameters (database locations)

Parameters Location ID

Line temperature 720

Line pressure 594

Prover inlet temperature 730

Prover outlet temperature 739

Prover inlet pressure 604

Prover outlet pressure 613

Density A temperature 749

Density B temperature 759

Header pressure 1543

Base density 354

Density A 288

Density B 306

Note: Attempts to enter any other location ID for Target Location will result in an input alarm, “MODB bad target”.

If Value is in units that are not listed in Table 7d.2 and the value is to be forwarded to a Target location,use Scaling factor to re-scale the forwarded value into base units. The setting for Unit is then ignored.

If Value is in units that are listed in Table 7d.2 and the value is to be forwarded to a Target location,select only the correct unit code for Unit, and ensure that Scaling factor is set to 0.



Table 7d.2: Codes for Unit parameter

Code Temperature Pressure Density 0 “Deg.C” (B) “bar abs” (B) “g/cc”1 “Deg.F” “Pa abs” “g/litre” 2 “Kelvin” “kPa abs” g/m3” 3 “Ohms” “MPa abs” “kg/cc” 4 “Deg.R” “psia” “kg/litre” 5 (No units) “kg/cm2 abs” “kg/m3” (B)6 (No units) “bar gauge” “tonnes/m3” 7 (No units) “Pa gauge” “oz/in3” 8 (No units) “kPA gauge” “oz/ft3” 9 (No units) “MPa gauge” “oz/barrel” 10 (No units) “psig” “oz/gallon (UK)” 11 (No units) “kg/c2 gauge” “oz/gallon (US)” 12 (No units) (No units) “lb/in3” 13 (No units) (No units) “lb/ft3” 14 (No units) (No units) “lb/barrel” 15 (No units) (No units) “lb/gallon (UK)” 16 (No units) (No units) “lb/gallon (US)” 17 (No units) (No units) “tons/ft3” 18 (No units) (No units) “tons/barrel” 19 (No units) (No units) “tons/gallon (UK” 20 (No units) (No units) “tons/gallon (US)”

(B) = Base units

Message Block List

The Daniel Senior Sonic™ transmitter is different to the Micro Motion® transmitter because it has registers grouped into blocks. In the operation manual for models 3400/3410/3420 (April 1998), there are 32 blocks of registers. Each block has a particular purpose and features multiple registers. For example, there is a Message Block 12 that has registers 350 - 398 for reading 48 calculation results, all floating-point values.

On the 7951 Flow Computer, the 7951 Message Block List will allow read or write access to any part of any Message Block on the Daniel transmitter. Each entry in the list comprises parameters to detail an access:

Start register – address of first register in Daniel Message Block (e.g. 350, for Message Block 12) Byte size – enter size of Daniel Message Block in bytes: ((End register - Start register +1) x 2) Number of items – enter quantity of registers that equate to a full value

As an example, consider reading register 392 (flow rate) from Daniel Message Block 12. The details to set-up on the 7951 Flow Computer are as follows:

1. Edit an entry in the Floating-point Register List

Value – Ensure status is “Live” to see raw flow rate value from transmitter. *Slave device – Select a MODBUS Slave Device record for the transmitter (see Section 7D.1.4) Register address – Not applicable when accessing Daniel Message Blocks. Message block – Select “Message Block 12” Byte offset – Select register to be accessed, 392, by entering an offset = (392 - 350) x 2 = 84 Target location – Not applicable for this example. Unit – Not applicable for this example. Scaling factor – Not applicable for this example.

* When a value is “Set”, the value is written to the register. However, if the register is read-only, as in this case, the Daniel transmitter will accept it but the register value will simply not be changed.



2. Edit entry (record) 12 of Message Block ListStart register – enter a value of 350 Byte size – enter size of message block in bytes = [398 - 350 + 1) x 2] = 98 Number of items – enter quantity of registers that equate to a full value (see note below).

7D.1.4 How to set-up a Slave Device record

A part of setting up the Transmitter Monitor is selecting a Slave Device record. The Slave Device record informs the 7951 Flow Computer (MODBUS Master) of what MODBUS slave it is going to be talking to and what communication settings it requires.

Figure 7d.3 (below) shows how to navigate from the MAIN MENU to the SLAVE DEVICES menu, with the keypad strokes needed to arrive at the menu.

With the 7951 Flow Computer acting as the MODBUS Master, as in this case, a MODBUS Slave Device record must be detailed as follows:

Device function – Select “Transmitter” option.

Port number – Select the 7951 serial port connected to the transmitter.

Slave device address – Enter numerical MODBUS address of the transmitter.

Word ordering – Keep “Modbus default” (factory default), unless transmitter requires Word swap.

Precision – Select “single” if accessing floating-point values that are 32-bit, or “double” for 64-bit.

Slave MODBUS commands – Select ‘Offset’ or ‘Full’ addressing method, as appropriate for transmitter.

Other record details are not applicable.

Note: The setting-up procedure is included in Section 7D.3.

Configure

Other parameters

Communications

x3

ax5

a

b

Modbus master c

Slave devices c


Figure 7d.3: Navigation to the SLAVE DEVICES menu

The correct setting for Number of items will depend on the configuration of the 7951 serial port and the transmitter, in respect of data type and data size (16-bits, 32-bits or 64-bits) of the value involved.

When the 7951 serial port is configured for multiple-register access and single-precision (32-bit) floating-point values, enter a value of 2 for floating-point value or 1 for an integer value.

When the 7951 serial port is configured for multiple-register access and double-precision (64-bit) floating-point values, enter a value of 4 for floating-point value or 1 for an integer value.

When the 7951 serial port is configured for single-register access, simply enter a value of 1.



7D.2 Preparing a Micro Motion® digital transmitter The following procedure is for preparing a Micro Motion® digital transmitter, Series 2000 multivariable, for MODBUS® digital communications with the 7951 Flow Computer.

This procedure requires a serial cable, a RS232/RS485 converter and Micro Motion’s ProLink II TM

transmitter configuration software on a PC.

Since the Series 2000 transmitter has a universal service port that supports other communication protocols, it must be configured to enable RS-485 MODBUS® communications. In addition to enabling this protocol, the baud rate must be changed from 38400 to 19200. (The minimum for the transmitter is 1200.)

Procedure:

1. Using a suitable cable and a RS232/RS485 converter, interconnect the PC port (e.g. COM1) to terminals 7 and 8 on the transmitter via the converter.

RS485 Converter MicroMotion TransmitterPin No: Terminal No: 2 7 7 8

2. Start the program ProLink II TM

3. Using Prolink II, establish communication between the PC and the transmitter through the menu <Connection><Connect to device>. Select the options, as shown below, and then click on the "Connect" button.

Note: This procedure might have to be repeated, as some RS232/RS485 converters do operate properly at the baud rate of 38400.

Protocol:Select “Universal Service Port”.

COM Port:Select “COM 1” (for PC port COM1).

4. Using ProLink II, configure the communication port of the transmitter. To do this: Select the menu <ProLink><Configuration> Select the tab labelled "485 Comm" Select the options shown below Click on “Apply” – repeat this until there are no error messages.

Protocol: Select “Modbus RTU”

Parity: Select “None”

Baud Rate: Select “19200”

Stop Bits: Select “1”

Note: Installation, operation, maintenance, etc. and safety instructions for the transmitter are outside the scope of this supplement and Flow Computer literature. For these details, refer to product literature of the transmitter. In addition, PC requirements for running ProLink II TM are outside the scope of this supplement and Flow Computer literature.



5. Terminate the program ProLink II TM

6. Using a suitable cable and a RS232/RS485 converter, connect the PC port (e.g. COM1) to terminals 5 and 6 on the transmitter.

RS485 Converter MicroMotion TransmitterPin No. Terminal No. 2 6 7 5

7. Using Prolink II TM, establish communication between the PC and the transmitter through the menu <Connection><Connect to device>.

Select options, as shown below, and then click on the "Connect" button.

Protocol: Modbus: Select “RTU (8-bit)”

Baud Rate: Select “19200”

Parity: Select “None”

Connect via Address/Tag: Select “Address/Tag 1”

COM Port: Select “COM 1”

Stop Bits: Select “1”

8. Using Prolink II TM, ensure process variables (e.g. Density) can be viewed through the menu <ProLink><Process variables>

9. Terminate the program ProLink II TM.



7D.3 Configuring the 7951 Flow Computer Follow these instructions to configure and activate the Monitor on the 7951 Flow Computer:

1. Using a suitable cable, connect a 7951 serial port to the transmitter. Note: For details of the 7951 serial ports that support RS485, refer to main Chapter 7.

Serial Port Micro Motion® TransmitterPin No. Terminal No. (Rx/Tx+) 5 (Rx/Tx-) 6

2. Program the 7951 Flow Computer to be a MODBUS Master device.

(2a) Navigate to this menu: <”Configure”>/<”Other Parameters”>/<”Communications”>/<”Ports”>.

(2b) Select a Serial Port menu, as appropriate for the serial port connected to the transmitter.

(2c) Configure the basic communication parameters for that serial port, as shown in Table 7d.3. (Some localised menu navigation is required to find the parameter screen.)

(2d) Navigate to: <”Configure”>/<”Other Parameters”>/<”Communications”>/<”Modbus master”>.

(2e) Configure the parameters, as shown in Table 7d.4.

(2f) Navigate to this sub-menu: <”Slave devices”>.

(2g) Select a Device menu (e.g. <”Device 1>).

(2h) Configure the parameters, as shown in Table 7d.5.

3. Program and activate the Monitor on the 7951 Flow Computer.

(3a) Navigate to this menu: <”Transmitter monitor”>.

(3b) Configure the <Mon poll method> and <Mon poll interval> parameters.

(3c) Navigate to the MESSAGE BLOCK menu (if applicable to transmitter).

(3d) Select the first available message block menu (e.g. MESSAGE BLOCK 1 menu).

(3e) Configure the parameters, as guided on page 7D-5.

(3f) Repeat Steps 3c to 3e for all other message blocks to be detailed.

(3g) Navigate to the INT REGISTERS menu (if applicable).

(3h) Select the first available register menu (e.g. INT REGISTER 1 menu).

(3i) Configure the parameters, as guided on page 7D-4.

(3j) Repeat Steps 3g to 3i for all other integer registers to be detailed.

(3k) Navigate to the FLOAT REGISTERS menu (if applicable).

(3l) Select the first available register menu (e.g. FLOAT REGISTER 1 menu).

(3m) Configure the parameters, as guided on page 7D-4.

(3n) Repeat Steps 3k to 3m for all other integer registers to be detailed.

(3o) Configure <Monitor enable> parameter to show “Enable”.




Table 7d.3: Basic Serial Port Communication Parameters


Setting

Comms port owner Select the multiple-choice option with “Modbus master”. “MODBUS slave” Port Baud rate Keep the factory default, unless transmitter using lower baud rates. “19200”

Port char format Keep the factory default, unless transmitter using another format. “8 bits none 1 stop” Port handshaking Keep the factory default setting. “None”

Port RS232 / 485 *** Select the RS485 signalling standard for the MODBUS network ** “RS 232” Port Modbus mode Keep the factory default setting. “RTU”

P Modbus word order Keep the factory default setting. “Modbus default” P MODB slave add (Not applicable) 1 P Modbus features (Not applicable) “None” P long reg access Keep the factory default setting, unless using single-register access. “Multiple registers”

P MODB total format (Not applicable) “32-bit integer” P MODB precision (Not applicable) “Single”

* The on-screen parameter descriptor includes a digit to identify the associated serial port.

** A 7951 may perform unexpected ‘restarts’ if it is configured to be “RS 232” when it should be “RS 485”.

*** Parameter is not applicable to serial ports that support RS-232 only.

Abbreviations used: “P” = Port, “reg” = register, “addr” = address, “char” = character, “MODB” = MODBUS

Table 7d.4: MODBUS Master details

Parameter(Database Location) Instructions and Comments Factory Default

Setting

Length of timeout Keep the factory default setting. “0.5 second” No of retries Keep the factory default setting. * “3 retries”

* If attempts to communicate with a slave are unsuccessful and exceed the maximum retries, an input alarm, “Modb failed slv”, is raised. The number of the slave 1 - 16 is given in the alarm message together with “R” (read failed) or “W” (write failed).

Abbreviation used here: “No” = number

Table 7d.5: Slave device details


Setting

Slave device func Select “Transmitter” from the multiple-choice list. “None” Slv device port no Select the 7951 serial port that is connected to the transmitter. “Comms port 1” Slv device address Edit the numeric MODBUS address of the transmitter. 0 Device word swap Keep the factory default, unless transmitter requires Word swap “Modbus default” Device precision Keep the factory default, unless floating-point value is 64-bit. “Single”

Slv modb commands Select “3,4, 16 addr offset” option for a Micro Motion® Transmitter ** “3, 16 full addr”

* The on-screen parameter descriptor includes a number to identify the slave device being detailed.

** The “offset” option applies where transmitters automatically add an offset (e.g. 40000) to get a register address specified in a received MODBUS request. For transmitters that do not do this and require a full address, keep the factory default.

Abbreviations used: “func” = function, “Slv” = Slave, “no” = number, “modb” = Modbus

Chapter 8 Alarms and Events

7951 2510 (Ch08/BC) Page 8.1

8. Alarms and Events

8.1 Alarms 8.1.1 Alarm types

The types of alarms which are detected and recorded are:

System alarms, caused by one or more of: Power failure. Battery low (if a battery is fitted). Watchdog. RAM checksum failure. ROM checksum failure.

Input alarms, caused by one or more of: Failure of analog inputs. Failure of density/viscosity transducers. Incorrect data has been entered.

Limit alarms, caused by one or more of: Limits which you have set. Limits defined by the system.

These always result in two alarms - one when the change first happens, and another when the system returns to its normal state.

8.1.2 Alarm indicators

The 7951 has three LED indicators to show alarm status; one each for Input, System, and Limit alarms. Each alarm indicator can be in one of three states:

Off The system is working normally.

Flashing An alarm has been received, but has not yet been accepted.

On All alarms have been accepted, but not yet cleared. The conditions that caused the alarms in the first place may still exist.

1. System alarm 2. Input Alarm 3. Limit Alarm

Figure 8.1: Alarm indicators on the front panel


Page 8.2 7951 2510 (Ch08/BC)

8.1.3 How alarms are received and stored

When a new alarm is received, the appropriate indicator LED on the front panel starts flashing. If the indicator is already flashing because of a previous alarm, it continues to do so. If the indicator is already ON (steady), it starts to flash.

Information about alarms is stored in two logs:

This gives: The Alarm Status Display (1) a summary of the contents of the Historical Alarm Log (2) an indication of the current status of the system.

The Historical Alarm Log This contains an individual entry for every alarm stored in the log.

The Historical Alarm Log can store up to 30 entries. When a new alarm is received, one of two things can happen:

If the Historical Alarm Log is NOT full:An entry for the new alarm is simply added to the list.

If the Historical Alarm Log is full:It depends on how the system is set up: Either (1) the oldest entry is deleted and the new one is added to the top of the list, or (2) the new alarm is discarded. In either case, the Status Display is updated automatically.

8.1.4 Examining the Alarm Status Display and Historical Alarm Log

Press the INFORMATION button If you want to examine the Alarm Status Display or the Historical Alarm Log.

To bring up the Alarm Status Display, select the Alarm Summary option.

To bring up the first entry in the Historical Alarm Log, select the Alarm History option.

To return to the INFORMATION MENU from these summary screens, you can use the BACK button.

Figure 8.2: How to get to the alarm log


7951 2510 (Ch08/BC) Page 8.3

8.1.5 What the Alarm Status Display tells you

A typical Alarm Status Display is shown in the Figure 8.2. The display lists, for each type of alarm (System, Input or Limit), the number of alarms which are live and new.

New alarms are alarms which have been received but not yet accepted.

Live alarms are alarms which refer to conditions which are still active.

An example of a live alarm is when there is a fault in the system. This produces two alarms - one when the fault first occurs (‘ON’) and the second when it is put right (‘Off’). If only the first alarm of the pair has been received, the alarm is said to be live because the condition still exists.

The number of live alarms tells you how many faults are still active. If you look at the Historical Alarm Log this tells you more about these faults.

8.1.6 What the entries in the Historical Alarm Log tell you

Figure 8.3 shows the function of the relevant buttons, and what is on the display.

Key to figure: 1. Indicates if there are entries BEFORE this one. 2. Alarm is either ‘ON’ (fault occurrence) or ‘OFF’ (fault cured). 3. Type of alarm. 4. Indicates alarm not accepted. 5. Accept this alarm. 6. Alarm description and extra identifier to qualify the alarm. 7. Clear this alarm entry. 8. Date and time that this alarm (message) was raised. 9. Identifies a stream/run

- not applicable to single-stream/run software.10. Indicates that there are alarm entries AFTER this one. 11. Scroll DOWN through the entries. 12. Scroll UP through the alarm entries. 13. Clear all alarm entries.

Figure 8.3: A typical entry in the log

Each alarm has its own entry in the Historical Alarm Log which tells you:

Type of alarmWhether it is a System alarm, Input alarm or Limit alarm and if the alarm is ‘on’ or ‘off’.

Extra identifier for the alarm This is not always shown for every entry but, where it is shown, it could be one of the following:

A digit This indicates the channel number on which the fault occurred.

A letter H and L are for high and low Limit alarms, S is for a step alarm.

Date and timeThe date is in the format DD-MM-YY and the time HH:MM:SS. These are entered automatically by the system when the alarm is received. The time is accurate to within one second.


Page 8.4 7951 2510 (Ch08/BC)

Acceptance indication This is only shown for those entries which have not been accepted. When the entry is accepted, the indicator disappears.

Other entries indicationAn up-arrow symbol shows that there are entries before the present one, a down-arrow symbol shows that there are others after. If the entry currently shown is first in the list, there is no up-arrow. If it is last, there is no down-arrow.

Description of the alarm This is an abbreviated description of the alarm and should be sufficient to help you trace the cause of the problem. A full list of all alarm messages and what they mean, are listed on page 8.3.

8.1.7 Clearing all entries in the Historical Alarm Log

To clear all the alarm entries in the Historical log, press the CLR button. This clears all entries in the Historical Alarm Log, zeroes the entries in the Status Display and sets all LED indicators to OFF.


7951 2510 (Ch08/BC) Page 8.5

8.1.8 User-defined Alarms

There are several types of user-defined alarms:

User-defined Alarms Page

User Alarm Type 1: ‘Measurement’ Limit Alarm 8.5

User Alarm Type 2: ‘Comparison’ limit alarm 8.6

8.1.8.1 User Alarm Type 1: ‘Measurement’ Limit Alarm

Two user limit alarms (nominated as ‘X’ and ‘Y’) are available for monitoring values of any parameters that do not have low/high alarm limits.

Configuring involves:

1. Editing the identification number of the parameter to be monitored by the 7951. 2. Editing values for the high and low limits.

IMPORTANT NOTICE

We recommend using the 7951 set-up Wizard, “Alarms”, when configuring these alarms. Wizards are described in Chapter 10.

Configuration task (“Limit Alarm X” or “Limit Alarm Y”)

Follow these instructions if you want to configure without using a Wizard.

1. Navigate to the parameter to be monitored, and then press the ‘a’ button once to display the parameter identification (ID) number. Make a note of that number.

2. Navigate to this menu: <“Configure”>/<“Other parameters”>/<“Alarms”>

3. Locate and edit parameters as shown in Table 8.1

Table 8.1: User Limit Alarm Parameters


User alarm ptr. Edit the value to be the ID number of the parameter to be monitored. The number will be replaced with the associated data name if the parameter exists. Note: Default setting is 0000 (“Off”) - not in use

User alarm HI lmt ‘Set’ the maximum allowed value for the selected parameter.

User alarm LO lmt ‘Set’ the minimum allowed value of the selected parameter.

* On-screen descriptions include an extra letter to identify the alarm nomination.

SummaryThe up-to-date state of all user-defined alarms is shown in this menu: <“Health check”>/<“User Alarms”>.

Alarms ‘X’ and ‘Y’ each have a dedicated digit:

‘0’ = Not in use/No Alarm/Alarm accepted ‘1’ = Alarm active


Page 8.6 7951 2510 (Ch08/BC)

8.1.8.2 User Alarm Type 2: ‘Comparison’ limit alarm

Two user comparison alarms (nominated as ‘A’ and ‘B’) are available for comparing values of two parameters and raising an alarm when the difference is outside a ‘Set’ limit.

Configuring involves:

1. Editing the identification numbers of the two parameters to be monitored. 2. Editing a value for the comparison limit.

IMPORTANT NOTICE

We recommend using the 7951 set-up Wizard, “Alarms”, when configuring these alarms. Wizards are described in Chapter 10.

Configuration task (“Comparison Alarm A” or “Comparison Alarm B”)

Follow these instructions if you want to configure without using a Wizard.

1. Navigate to the two parameters to be compared. Use the ‘a’ button to display the parameter identification (ID) number. Make a note of each ID number.

2. Navigate to this menu: <“Configure”>/<“Other parameters”>/<“Alarms”>

3. Locate and edit parameters as shown in Table 8.2.

Table 8.2: User Comparison Alarm Parameters


Comp alarm ptr1 Edit the value with the ID number of the first parameter to be used in the

comparison. The number will be replaced with the associated parameter name (if the parameter exists). Note: Default setting is 0000 (“Off”) - not in use

Comp alarm ptr2

Edit the value line with in the ID number of the second parameter to be used in the comparison. The number will be replaced with the associated parameter name (if parameter exists).

Note: Default setting is “Off”. (i.e. not in use)

Comp alarm limit ‘Set’ the maximum allowed difference between values of the two parameters

without needing to raise an alarm. Note: Default limit is 0 – feature is switched off

* On-screen descriptions include an extra letter to identify the alarm nomination

SummaryThe up-to-date state of all user-defined alarms are shown in this menu:<“Health check”>/<“User Alarms”>

Alarms ‘A’ and ‘B’ each have a dedicated digit:

‘0’ = Not in use/No Alarm/Alarm accepted ‘1’ = Alarm active


7951 2510 (Ch08/BC) Page 8.7

8.1.9 Alarm Logger Output (ALO)

Status Outputs 1 to 5 are dedicated to indicating the presence of active alarms. By default, the ALO is enabled and pre-configured as shown in Table 8.3.

Table 8.3: ALO Default Set-up

Digital Output Default Function

Status Output 1 Indicate System Alarms only Status Output 2 Indicate Limit Alarms only *Status Output 3 Indicate Input Alarms only Status Output 4 Indicate User Limit Alarm ‘X’ Status Output 5 Indicate User Limit Alarm ‘Y’

* User Comaprison Alarms ‘A’ and ‘B’ are also indicated

ALO Re-configuration Options ALO use of the first three Status Outputs can be re-configured at any time by changing the selected alarm grouping. Parameters for making a change are found within the menu system.

To change the alarm grouping: 1. Navigate to this menu: <”Configure”>/<”Other parameters”>/<”Alarms”>/<”Alarm logger”>

2. Locate parameters as identified in Table 8.4, and change the alarm grouping option to suit your requirements. Available options are summarised in Table 8.5.

Table 8.4: ALO Configuration Parameters

Parameters Purpose of Configuration Parameters

Alarm output 1 Show/Change alarm group for Status Output 1 Alarm output 2 Show/Change alarm group for Status Output 2 Alarm output 3 Show/Change alarm group for Status Output 3

Table 8.5: Alarm Grouping Options

Option Purpose of option

None Do not indicate presence of any alarms * System Indicate System alarms only Input Indicate Input alarms only Limit Indicate Limit alarms only Any Include System, Input and Limit alarms.

System Input Indicate System alarms and Input alarms System Limit Indicate System alarms and Limit alarms

Input Limit Indicate Input alarms and Limit alarms

* This does not free up the digital (status) output for another function

Notes:1. For further information on Digital (Status) Outputs, refer to Chapter 2 and Appendix ‘C’.

2. The presence of active User-defined Comparison Alarms (‘A’, ‘B’, etc.) are indicated by Status Outputs nominated to include Limit Alarms.


Page 8.8 7951 2510 (Ch08/BC)

8.1.10 Alarm Message List

* Alarm can be cleared immediately

Base Alarm Message

Alarm Type What the “ON” alarm message means

4x5 Oil dens fail Input Oil density (by 4x5 referral) can not be calculated. Check all associated parameters. Extra Message Character: “P” = Prime measurement, “M” = Metering measurement

5167 orif dia lmt Limit Orifice diameter is outside a limit as defined in the chosen ISO 5167 Standard. Extra Message Character: “H” = High limit, “L” = Low limit

5167 pipe dia lmt Limit Pipe diameter is outside a limit as defined in the chosen ISO 5167 Standard. Extra Message Character: “H” = High limit, “L” = Low limit

Alarm total limit Limit Alarm condition total has reached the programmed (SET) rollover-to-zero limit. Extra Message Character: none = Normal mode (main) total, “M” =Maintenance mode total, “T”/ “B” = Batch total

API Oil dens fail Input Oil density (by API referral) can not be calculated. Check all associated parameters. Extra Message Character: “P” = Prime measurement, “M” = Metering measurement

Archive format * System Archive formatting operation unsuccessful. Check all size associated parameters.

Archive too small * System Insufficient space for archiving. Check all size associated parameters.

Base BSW limit Limit BSW % at base conditions is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

Base den API fail Input API referral calculation for base density was unsuccessful. Check all associated configurable parameters using reference pages in Chapter 11. Extra Message Character: “F” = Forward referral stage, “R” =Reverse referral stage

Base dens limit Limit The Base Density measurement value is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

Battery failed System Configuration has been lost. Replace the battery as instructed in Chapter 14.

Battery low System Replace the battery as instructed in Chapter 14. (Configuration is safe for moment)

Brooks:10 run lmt * Limit Maximum number of prove runs restored to 10 runs - the maximum allowed for Brooks Compact Proving

BSW comp limit Limit (A#B) The calculated difference between BSW measurement channels (‘A’ & ‘B’) is beyond the programmed (SET) comparison limit.

Comparison limit Limit General user-defined limit alarm. Extra Message Character: “A” = User Alarm ‘A’, “B” = User Alarm ‘B’

Database corrupt * System Corruption occurred but has been fixed automatically. Always seen when software has just been installed. Check all configured parameters If seen at any other time.

DBM bad chksum * System There has been an unrecoverable memory checksum failure. The Flow Computer will need to be re-configured. Extra Message Character: ‘V’ = Volatile (RAM), ‘N’ = Non-volatile (FRAM)

DBM bad triple * System Corruption of the database in a memory area occurred but there has been an automatic recovery. (‘0’ is often seen after installing new release of same software version) Extra Message Character: ‘0’ = RAM copy, ‘1’=1st. non-volatile memory copy, ‘2’=2nd. Non-volatile memory copy, ‘3’ = Padding, ‘!’ = Beyond repair / Re-configure Flow Computer

Dens 4x5 fail Input Metering Density by 4x5 matrix referral calculation was unsuccessful. Check all associated configurable parameters using reference pages in Chapter 11.

Dens API fail Input Metering Density by API referral calculation was unsuccessful. Check all associated configurable parameters using reference pages in Chapter 11.

Density cal fail System Calibration of Time Period Input unsuccessful. Extra Message Character: “1”= Time Period Input ‘1’, “2” = Time Period Input ‘2’, etc.

Dens comp limit Limit (A#B) The calculated difference between density measurement channels (‘A’ & ‘B’) is beyond the programmed (SET) comparison limit.


7951 2510 (Ch08/BC) Page 8.9

(Alarm Message List continued…) * Alarm can be cleared immediately

Base Alarm Message


Dens press limit Limit ‘Density loop’ pressure measurement value is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit, “S” = Step limit

Dens temp A limit Limit ‘Density loop’ fluid temperature measurement channel ‘A’ value is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit, “S” = Step limit

Dens temp B limit Limit ‘Density loop’ fluid temperature measurement channel ‘B’ value is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit, “S” = Step limit

Dens txdr calc Input A density (transducer) measurement channel value has a “Fail” status. Check the physical connections with the transducer and use the “Health check” menu to monitor the associated Time Period Input. Extra Message Character: “A” = Density ‘A’, “B” = Density ‘B’

Dens txdr limit Limit The prime density measurement value is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

Diff press limit Limit Differential pressure measurement value is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit, “S” = Step limit

DLG list non-real * Input Archive parameter lists only allow parameters with floating-point values.

Dynamic visc calc Input A dynamic viscosity measurement channel value has a “Fail” status. Check the physical connections with the transducer and use the “Health check” menu to monitor the associated Time Period Input. Extra Message Character: “A” = Dynamic Viscosity ‘A’, “B” = Dynamic viscosity ‘B’

Dyn visc compare Limit (A#B) The calculated difference between measurement channels (‘A’ & ‘B’) is beyond the programmed (SET) comparison limit.

Dyn visc limit Limit Dynamic viscosity measurement value is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

Gross std vol lmt Limit Gross Standard Volume flow rate is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

Gross vol limit Limit Gross Volume flow rate is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

GSV total limit Limit Gross Std. Volume flow total has reached the programmed (SET) rollover-to-zero limit. Extra Message Character: none = Normal mode (main) total, “M” =Maintenance mode total, “T”/ “B” = Batch total

GV total limit Limit Gross Volume flow total has reached the programmed (SET) rollover-to-zero limit. Extra Message Character: none = Normal mode (main) total, “M” =Maintenance mode total, “T”/ “B” = Batch total

HART input fail Input A HART Input parameter (location) page has a “Fail” status. The Flow Computer is not presently receiving information from a HART protocol transmitter. Check the HART network loop connection and monitor the HART Input using the “Health Check” menu. Extra Message Character: “1” = HART Input ‘1’, “2” = HART Input ‘2’, … , “8” = HART Input ‘8’

HSL addr conflict System High Speed List address conflict due to a HSL block overlapping. Extra Message Character: “A” = Block ‘A’, “B” = Block ‘B’, … , “F” = Block ‘F’

Ind std vol limit Limit Indicated Standard Volume flow rate is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

ISO5167 beta lmt Limit Beta ratio is outside a limit as defined in the chosen ISO 5167 Standard.

ISO5167 ReD limit Limit Reynolds number is outside a limit as defined in the chosen ISO 5167 Standard.

ISV total limit Limit Indicated Standard Volume flow total has reached the programmed (SET) rollover-to-zero limit. Extra Message Character: none = Normal mode (main) total, “M” =Maintenance mode total, “T”/ “B” = Batch total


Page 8.10 7951 2510 (Ch08/BC)


Base Alarm Message


IV total limit Limit Indicated Volume flow total has reached the programmed (SET) rollover-to-zero limit. Extra Message Character: none = Normal mode (main) total, “M” =Maintenance mode total, “T”/ “B” = Batch total

Kin visc compare Limit (A#B) The calculated difference between measurement channels (‘A’ & ‘B’) is beyond the programmed (SET) comparison limit.

Kin visc limit Limit Kinematic viscosity measurement value is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

mA input cal fail Input Calibration of mA (Analogue) Input unsuccessful. Extra Message Character: “1” = Analogue Input ‘1’, “2” = Analogue Input ‘2’, … , “a” = Analogue Input ‘10’

mA input failed Input An Analogue Input channel parameter (location) page has a “Fail” status. The Flow Computer is not presently receiving valid signals from a loop-powered transmitter. Check physical connections and monitor the input using the “Health Check” menu. Extra Message Character: “1” = Analogue Input ‘1’, “2” = Analogue Input ‘2’, … , “a” = Analogue Input ‘10’

mA input no cal System Analogue Input not calibrated. Contact the factory for advice. Extra Message Character: “1” = Analogue Input ‘1’, “2” = Analogue Input ‘2’, … , “a” = Analogue Input ‘10’

mA out cal fail System Calibration of mA (Analogue) Output unsuccessful. Extra Message Character: “1” = Analogue Output ‘1’, “2” = Analogue Output ‘2’, etc.

mA output failed Output An Analogue Output channel parameter (location) page has a “Fail” status. There is a hardware problem with the Flow Computer. Contact the factory for advice. Extra Message Character: “1” = Analogue Output ‘1’, “2” = Analogue Output ‘2’, etc.

mA output no cal System Analogue Output not calibrated. Contact the factory for advice. Extra Message Character: “1” = Analogue Output ‘1’, “2” = Analogue Output ‘2’, etc.

Mass limit Limit Mass rate is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

Mass total limit Limit Mass flow total has reached the programmed (SET) rollover-to-zero limit. Extra Message Character: none = Normal mode (main) total, “M” =Maintenance mode total, “T”/ “B” = Batch total

Mass water% limit Limit Percentage of ‘water’ in oil/water mix (by mass) is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

Meter BSW limit Limit BSW % at metering conditions is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

Meter press limit Limit The metering pressure measurement value is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit, “S” = Step limit

Meter temp limit Limit The metering temperature measurement value is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit, “S” = Step limit

MODB slave clash System Serial Port configuration conflicts with the configuration of another port Extra Message Character: “1” = Serial Port ‘1’, “2” = Serial Port ‘2’, etc.

Oil SG limit Limit Specific gravity of the metered oil is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

Orif ISO5167 lmt Limit The ISO 5167 Standard calculation was unsuccessful. Check all Orifice System parameters using reference pages in Chapter 11.

Peer target fail System Peer-to-peer communication failed. Extra Message Character: <MODBUS Slave device number>

PID input error Input Set-up problem. Check the indicated PID configuration parameter. Extra Message Character: “I” = PID Input parameter value must be a floating-point number “S” = PID Setpoint parameter value must be a floating-point number.


7951 2510 (Ch08/BC) Page 8.11


Base Alarm Message


Power fail * System The Flow Computer has been without electrical power for a period of time. Examine the date and time stamp of the “ON” and “OFF” messages for the outage period.

Prime BSW limit Limit The prime BSW measurement value is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

Prover abort Proving session stopped. Extra Message Character:“I” = Initialisation problem, “I” = Pre-run problem, ”L” = Leak detected “c” = All prove runs completed, “S” = Stream information missing ”s” = Stabilisation not achieved, “p” = Target Plenum pressure is outside alarm limits

Prover in press Limit The pressure at the Prover inlet valve is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit, “S” = Step limit

Prover in temp Limit The temperature measurement value for fluid at the Prover inlet valve is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit, “S” = Step limit

Prover limit Limit Proving parameter out of limits. Extra Message Character: “F” = Flow rate, “T” = Temperature, “P” = Pressure, “M” = Meter factor “e” = Proving Error (Missing Pulses)

Prover out temp Limit The temperature measurement value for fluid at the Prover outlet valve is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit, “S” = Step limit

Prover out press Limit The pressure at the Prover outlet valve is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit, “S” = Step limit

Prover timeout Limit ‘Displacer’ failed to reach a detector switch within a programmed (SET) time limit. Extra Message Character: “S” = Start sensor, “E” = End sensor

Prt input failed Input An Analogue Input channel parameter (location) page has a “Fail” status. The Flow Computer is not presently receiving valid signals from a RTD/PRT field transmitter. Check physical connections and monitor the input using the “Health Check” menu. Extra Message Character: “1” = Analogue Input ‘1’, “2” = Analogue Input ‘2’, … , “a” = Analogue Input ‘10’

Prt no cal System Analogue Input not calibrated. Contact the factory for advice. Extra Message Character: “1” = Analogue Input ‘1’, “2” = Analogue Input ‘2’, … , “a” = Analogue Input ‘10’

Pulse out limit Limit The frequency of pulses issued through a Pulse Output has reached the maximum rate. Extra Message Character: “M” = Main Turbine (wired to Pulse Input ‘1’)

Qty batch overrun System Batch has overrun by an amount that has exceeded a ‘programmed (SET) limit.

Qty batch running System An attempt has been made to start a different type of batch whilst a quantity-based batch is in progress. Extra Message Character:”T” = Timed batch, “M” = Manual triggered batch

Qty batch start System Quantity batch could not be started. Extra Message Character:“F” = Flow not halted. There must be no flow before starting Flow Delivery Control, “R” = Quantity batch already running

Retro calc fail System Retrospective calculation attempted but was unsuccessful Extra Message Character:”F” = Batch archive empty or record not found, “U” = Update to existing record failed, “W” = Unable to write new record to batch archive

SG limit Limit Specific gravity measurement is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

SpEqu1 calc fail Input Incorrect set-up of Special Equation ‘1’ has caused it to fail.

SpEqu2 calc fail Input Incorrect set-up of Special Equation ‘2’ has caused it to fail.


Page 8.12 7951 2510 (Ch08/BC)


Base Alarm Message


StdVol water% lmt Limit % of ‘water’ in oil/water mix (by standard volume) is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

Strainer blocked * Input Blockage detected (by Live Input). Check Strainer.

Timeperiod failed Input A Periodic Time Input channel parameter (location) page has a “Fail” status. The Flow Computer is not presently receiving frequency signals from a transmitter. Check physical connections and monitor the input using the “Health Check” menu. Extra Message Character: “1” = Time Period Input ‘1’, “2” = Time Period Input ‘2’, etc.

Timeperiod glitch * Input A series of anomalous transmitter readings has occurred. Adjust the setting of the glitch filter parameter that is associated with the Density or Viscosity transducer.

Timeperiod no cal System Periodic Time Input not calibrated. Contact the factory for advice. Extra Message Character: “1” = Time Period Input ‘1’, “2” = Time Period Input ‘2’, etc.

Turb err-dev calc Input An ‘error percentage’ could not be obtained from the linearisation of a calibration curve. Extra Message Character: “M” = Main Turbine (wired to Pulse Input ‘1’)

Turb freq limit Limit A calculated pulse frequency has exceeded the programmed (SET) upper limit Extra Message Character: “M” = Main Turbine (wired to Pulse Input ‘1’)

Turb K-factor err Input A ‘K Factor’ could not be obtained from the linearisation of a calibration curve profile. Extra Message Character: “M” = Main Turbine (wired to Pulse Input ‘1’)

Turb limit failed Limit Missing pulse count has exceeded a programmed (SET) upper limit. Extra Message Character: “1” = Pulse Input ‘1’, “2” = Pulse Input ‘2’, etc.

Turb pcent failed Input The percentage of missing pulses in respect of counted pulses during a cycle has exceeded a programmed (SET) upper limit. Extra Message Character: “1” = Pulse Input ‘1’, “2” = Pulse Input ‘2’, etc.

Turbine no cal System A Pulse (Turbine) Input is not calibrated. Contact the factory for advice. Extra Message Character: “1” = Pulse Input ‘1’, “2” = Pulse Input ‘2’, etc.

Turb visc curve Input A ‘K Factor’ could not be obtained from the linearisation of a calibration curve profile. Extra Message Character: “M” = Main Turbine (wired to Pulse Input ‘1’)

User alarm Limit General user-defined limit alarm. Extra Message Character: “X” = User Alarm ‘X’, “Y” = User Alarm ‘Y’

Valve failed Input No response from a valve controller. Extra Message Character: “1” = Prover Inlet, “2” = Prover Outlet, “3” = Stream Block, “4” = 4-way Diverter

Valve timeout Input No response from a valve controller within expected time limit. Extra Message Character: “1” = Prover Inlet, “2” = Prover Outlet, “3” = Stream Block, “4” = 4-way Diverter

Visc 4x5 fail Input Metering Kinematic Viscosity by 4x5 matrix referral calculation was unsuccessful. Check all associated configurable parameters using reference pages in Chapter 11.

Visc ASTM fail Input Metering Kinematic Viscosity by ASTM D341 referral calculation was unsuccessful. Check all associated configurable parameters using reference pages in Chapter 11.

Visc dens calc Input A ‘Viscosity loop’ density measurement channel value has a “Fail” status. Check the physical connections with the Viscosity transducer and configuration parameters. Use the “Health check” facility menu to monitor the associated Time Period Input. Extra Message Character: “A” = Viscosity Loop Density ‘A’, “B” = Viscosity Loop Density ‘B’

Visc density Input The prime ‘Viscosity Loop’ measurement value is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit

Visc temp A limit Limit ‘Viscosity loop’ fluid temperature measurement channel ‘A’ value is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit, “S” = Step limit

Visc temp B limit Limit ‘Viscosity loop’ fluid temperature measurement channel ‘B’ value is outside a programmed (SET) limit. Extra Message Character: “H” = High limit, “L” = Low limit, “S” = Step limit


7951 2510 (Ch08/BC) Page 8.13

8.2 Events 8.2.1 Introduction to 7951 events

The 7951 keeps a record of important system changes in an Event Log. This is very similar, in concept, to the alarm log, but the nature of the information kept is different.

Event details that can be viewed in the event log:

Changes to the status of pre-determined† data that affects calculations

Changes to the value of data pre-determined data that affects calculations.

Event details that can be seen only in a printout of the event log:

Messages from hardware diagnostics.

Download of a configuration completed.

8.2.2 Event indicators

Unlike alarms, there are no event indicators on the front panel of the 7951.

8.2.3 How events are received and stored

Information about events is stored in two logs:

This gives: Event Status Display (1) a summary of the contents of the Historical Event Log (2) an indication of the current status of the system.

Historical Event Log This contains an individual entry for every event stored in the log.

There is enough room, in the historical event log, to store up to 150 event records. When a new event is received, one of two things can happen:

If the event log is NOT full : A new event record is simply added.

If the event log is full : The event configuration data, Event full action, has two options, “Replace” and “Ignore”, for determining how to deal with a new event when the event log is full. (See Table 8.6)

Table 8.6: Event Full Action - Available Options

<Event full action> Option

Purpose of Option

Replace Always overwrite the oldest event in the event log.

Ignore Always discard a new event when the event log is full.

Note: The default action is “Replace”

† This can not be changed. The list of auditable data is fixed.


Page 8.14 7951 2510 (Ch08/BC)

8.2.4 Examining the Event Summary and the Event Log

Press the INFORMATION button If you want to examine the Event Status Display or the Historical Event Log.

To bring up the Event Status Display, select the Event Summary option.

To bring up the first entry in the Historical Event Log, select the Event History option.

To return to the INFORMATION MENU from the two screens , you can use the BACK button.

Figure 8.4: How to get to the event log

8.2.5 What the Event Status Display tells you

A typical Status Display is shown in the diagram (below). It lists, for each type of event (Auto, User or Periodic) the numbers of alarms which are active and live.

Active events are events which have been received but not yet accepted. Live events are events which refer to conditions which are still active.

The number of live events tells you how many of them are still active. If you look at the Historical Event Log this tells you more about these events.


7951 2510 (Ch08/BC) Page 8.15

8.2.6 What the entries in the Historical Event Log tell you

Figure 8.5 shows the function of the relevant buttons, and what is on the display.

Key to figure:

1. Indicates if there are entries BEFORE this one. 2. Location identifier.3. Type of event. 4. Indicates alarm not accepted. 5. Accept this alarm. 6. Event description. 7. Clear this alarm entry 8. Date and time that this alarm (message) was raised. 9. Indicates that there are alarm entries AFTER this one. 10. Scroll DOWN through the entries. 11. Scroll UP through the alarm entries. 12. Clear all alarm entries.

Figure 8.5: A typical entry in the Historical Event Log

Each event has its own entry in the Historical Event Log which tells you:

Type of eventWhether it is Auto, User or Periodic and on or off.

Type What it means

Auto Changes made by the 7951 application software.

User Changes made by the keypad or done over serial communications.

Periodic This event type is not used at present.

Date and timeThe date is in the format DD-MM-YY and the time HH:MM:SS. These are entered automatically by the system when the alarm is received. The time is accurate to within one second.

Acceptance indicationThis is only shown for those entries which have not been accepted. When the entry is accepted, the indicator disappears.

Other entries indicationAn up-arrow shows that there are entries before the present one, a down-arrow shows that there are others after. If the entry currently shown is first in the list, there is no up-arrow. If it is last, there is no down-arrow.

Description of the eventThis is an abbreviated description of the event but should be sufficient to help you trace the reason for it. A full alarm message listing starts on page 8.8.

Old value and new value Pressing the RIGHT-ARROW button displays another screen with the old and new values of data (Figure 8.6). Press the LEFT-ARROW (or the RIGHT-ARROW) button for the previous display to re-appear.


Page 8.16 7951 2510 (Ch08/BC)

Figure 8.6: Old value and new value screen

8.2.7 Clearing all entries in the Historical Event Log

To clear all the event entries in the Historical Event log, press the CLR button. This clears all entries in the Historical Event Log and zeroes the entries in the Event Status Display.


7951 2510 (Ch08/BC) Page 8.17

8.3 Enhanced Auditing There is an optional enhanced auditing facility for recording user initiated changes to the 7951 Flow Computer software parameters that have an influence on the metering results. This enhanced feature is the result of an essential requirement from North Sea Practices and the Department of Trade and Industry (DTI).

This feature allows a 7951 Flow Computer to continuously monitor and report on changes to existing SET values, changes to option selections and changes to several parameter attributes (value status and individual audit control settings). The facility will report changes by recording Audit User Events and Audit System Alarms that will enable the back-calculation of fiscal values and account for changes that have occurred.

8.3.1 Audit User Events

All generated events are stored in the Historical Event Log, as fully explained in Section 8.2. Audit events are either sub-classed as “USER” triggered or “AUTO” triggered.

An example of a “USER” event is the act of manually changing a software parameter status to be “SET” instead of “LIVE”.

An example of an “AUTO” triggered event is the 7951 automatically changing a software parameter status to “Fail” when a live input source fails.

Every event has a date and time for the occurrence, an on-screen location descriptor and a summary of the change. This information is divided into four pages, as seen in Figure 8.7. Use the ARROW buttons, as shown, to navigate around the pages.

To enable Audit User Events:

Naviage to the menu <”Configure”>/<”Other parameters”>/<”DB attributes”> Locate the parameter with “Attribute display”. Select “On” from the multiple-choice option list. Locate the parameter page with “Audit inactive locs”. Select “On” from the multiple-choice option list.

Figure 8.7: Example of Audit Event pages from Historical Log


Page 8.18 7951 2510 (Ch08/BC)

8.3.2 Audit System Alarms

All generated alarms are stored in the Historical Alarm Log, as fully explained in Section 8.1. Auditing Control alarms are sub-classed as “SYSTEM” alarms.

An Audit Control alarm is normally raised whenever the value status attribute of a parameter is changed to “Set”. This alarm entry can be identified visually with the word “ON” on the first display line.

A subsequent value status change, from “SET” to “LIVE”, to “FB” or to “FAIL” will then raise a matching system alarm. That matching alarm entry can be identified visually with the word “OFF” on the first display line.

To enable Audit System Alarms:

Naviage to the menu <”Configure”>/<”Other parameters”>/<”DB attributes”>.

Locate the parameter page with “Attribute display”.

Select “On” from the multiple-choice option list.

Locate the parameter page with “Audit active locs”.

Select “On” from the multiple-choice option list.

New “ON” alarm raised because status of parameter has changed to “Set”

Matching “OFF” alarm raised because status of parameter has changed from “Set”

Figure 8.8: Example of Audit System Alarm pages from Historical Log

Figure 8.9 shows how the Audit Control alarm message can appear in one of two optional formats.

To change format: Navigate to this menu: <”Configure”>/<”Other parameters”>/<”DB attributes”>.

Locate the parameter page with “DB loc alarm text” as the descriptor.

Select an option descriptor from the multiple-choice list.

Any change is activated for the next 7951 machine cycle.

Alarm Message Format: “Descriptor Text” option

Alarm Message Format: “Loc:XXXX is set” option

Figure 8.9: Optional Formats for Alarm Control Message


7951 2510 (Ch08/BC) Page 8.19

8.3.3 Audit Control Attributes

Each 7951 Flow Computer software parameter has two independent, programmable attributes for adjusting how the auditing of it operates. Adjustments can be determined either by the 7951 (in automatic mode) or by the user (in manual mode). Select a method by editing the multiple-choice list of the <”Auditing attrib ctrl”> parameter page, located within the <”Configure”>/<”Other Parameter”> menu.

Figure 8.10 shows where to find Audit Control attributes. Navigate to any parameter, and then use the DOWN-ARROW and UP-ARROW button to switch between pages.

(1) Auditing Alarm Suppression Control (2) Auditing Event Suppression Control (3) Security Level required for editing

Figure 8.10: Typical parameter page showing all attributes

By default, Audit Control attributes are not accessible in the menu system. To make them accesible, follow these steps:

Naviage to the menu <”Configure”>/<”Other parameters”>/<”DB attributes”> Locate the parameter with “Attribute display”. Select “On” from the multiple-choice option list.

Note: This action also automatically enables the auditing control functions (if not already enabled by the software parameters <Alarm active locs”> and <”Audit unactive locs”>).


Page 8.20 7951 2510 (Ch08/BC)

The programmable attributes are:

1. Auditing Event Suppression Control (Audit/No Audit)

When the automatic mode is in use:

Critical “USER” events, such as a “LIVE” to “SET” status change, are never suppressed. They always appear in the Historical Event Log.

Less critical “USER” events, such as a valve command selection, can be suppressed by editing the attribute setting to be “No Audit”.

However, be aware that the 7951 Flow Computer can, by default, automatically override and change the setting under certain conditions. There is a logic table for this in the “Audit Event Suppression Control” section on the next page.

Note: An “AUTO” (7951 triggered) event is never suppressed.

When the default manual mode is in use:

A “USER” event can be suppressed by editing the attribute setting to be “No Audit”.

2. Auditing Alarm Suppression Control (Alarm/No Alarm)

When the automatic mode is in use:

The “SET” audit alarm can be suppressed by editing the attribute setting to be “No Alarm”. However, be aware that the 7951 Flow Computer can, by default, automatically override and change the setting under certain conditions. There is a logic table for this in the “Audit Alarm Suppression Control” section on the next page.

When the default manual mode is in use:

The “SET” audit alarm can be suppressed by editing the attribute setting to be “No Alarm”.

There is a third attribute on the same page, which can also be edited. This is the security level (e.g. “Engineer”) that is required to make changes to the software paramater.

Security levels are as explained in Chapter 11. The exception to this is the “Super User” security level, which is not selectable and is not attainable by anyone apart from the 7951 Flow Computer itself.

Note: The existing setting for each Audit Control attribute is displayed within the menu system and is also available for retrieval by an external Modbus networked device. (See Chapter 7)

The parameter <"Secure all locations"> results in the required security level of all parameters being set to programmer, except those that are “super user”.


7951 2510 (Ch08/BC) Page 8.21

8.3.4 Audit Event Suppression Control: Automatic Mode

Under automatic mode, adjustments to the setting of the Audit Event Suppression Control attribute are in accordance with a built-in logic table.

Table 8.7 shows:

(a) The impact on the “Audit” or “No Audit” setting when using the front panel keyboard (or Modbus protocol communications) to manipulate the value status of a software parameter.

(b) When a “USER” event is generated as the result of a user initiated action.

(c) When an “AUTO” event is generated as the result of a 7951 initiated action.

Automatic mode is selected by editing the multiple-choice list of the <”Attribute control”> parameter, located within the <”Configure”>/<”Other Parameters”>/<”Db attributes”> menu.

Table 8.7: Logic for 7951 changes to attribute settings and if events are recorded

Value Status Change

Attribute Setting (Before Change)

Attribute Setting (After Change)

USER Event on change?

AUTO Event on change?

Notes?

Live to Set No Audit Audit Yes No

Live to Set Audit Audit Yes No

Live to FB No Audit No Audit No Yes

Live to FB Audit Audit No Yes

Live to Fail No Audit No Audit No No Alarm raised instead

Live to Fail Audit Audit No No Alarm raised instead

Fail to Set No Audit Audit Yes No

Fail to Set Audit Audit Yes No

Fail to Live No Audit No Audit No No Alarm raised instead

Fail to Live Audit Audit No No Alarm raised instead

FB to Set No Audit Audit Yes No

FB to Set Audit Audit Yes No

FB to Live No Audit No Audit No Yes

FB to Live Audit Audit No Yes

Set to Live No Audit No Audit No No

Set to Live Audit No Audit Yes No

Set to Fail No Audit No Audit No No

Set to Fail Audit No Audit Yes No

Set to FB No Audit No Audit No Yes

Set to FB Audit No Audit Yes Yes Read Table Note A

Table Notes: A A “USER” event is generated for a “SET” to “LIVE” action by the user. An “AUTO” event is generated for the

“Live” to “FB” action by the 7951.

B Selecting an alternative unit of measurement (for display) is recorded as a “USER” event even with a “No Audit” setting.

C An event is recorded for all user initiated changes to the “No Audit” or “Audit” setting.

Table 8.8 shows if an event is logged when a user makes changes to the “No Audit” or “Audit” setting without changing the value or value status.


Page 8.22 7951 2510 (Ch08/BC)

(Table Notes continued…)

D Status changes that are not possible: “FB to Fail” and “Fail to FB”

E Changing a ‘Set’ value to another ‘Set’ value is always recorded as a “USER” event. Table 8.9 shows if an event is recorded when the value status (e.g. “SET”) is not changed but the value does change or an option is selected from a multiple-choice list.

Table 8.8: Logic for recording an event when the attribute setting is changed

Value Status Attribute Setting (Before)

Attribute Setting (After)



(Any) No Audit Audit Yes No

(Any) Audit No Audit Yes No

Table 8.9: Logic for recording events when a value/option selection changes

Value Status

Action to trigger an event

Attribute Setting



Set Edit new value Audit Yes No

Set Edit new value No Audit Yes No

Live Value fluctuates Audit No No

Live Value fluctuates No Audit No No

FB FB value edited Audit No No

FB FB value edited No Audit No No

Fail Value fluctuates Audit No No

Fail Value fluctuates No Audit No No

(None) Select new option Audit No No

(None) Select new option No Audit No No

Key:- FB = Fallback state


7951 2510 (Ch08/BC) Page 8.23

8.3.5 Audit Alarm Suppression Control: Automatic Mode

Under automatic mode, adjustments to the setting of the Audit Alarm Suppression Control attribute are in accordance with a built-in decision table.

Table 8.10 shows:

(a) The impact on the “Alarm” or “No Alarm” setting when using the front panel keyboard (or a Modbus protocol command) to manipulate the value status.

(b) When an “ON” flagged SYSTEM alarm is raised as the result of a user initiated action.

(c) When an “OFF” flagged SYSTEM alarm is raised as the result of a user initiated action.

Automatic mode is selected by editing the multiple-choice list of the <”Attribute control”> parameter page, located within the <”Configure”>/<”Other Parameters”>/<”Db attributes”> menu.

Table 8.10: Logic for 7951 changes to attribute settings and if an alarm is recorded

Value Status Attribue Setting (Before Change)

Attribute Setting (After Change)

Alarm raised on change?

Notes?

Live to Set No Alarm No Alarm No

Live to Set Alarm Alarm Yes (ON) Read Note B

Live to FB No Alarm No Alarm No

Live to FB Alarm Alarm No

Live to Fail No Alarm No Alarm No

Live to Fail Alarm Alarm No

Fail to Set No Alarm No Alarm No

Fail to Set Alarm Alarm Yes (ON) Read Note B

Fail to Live No Alarm No Alarm No

Fail to Live Alarm Alarm No

FB to Set No Alarm No Alarm No

FB to Set Alarm Alarm Yes (ON) Read Note B

FB to Live No Alarm No Alarm No

FB to Live Alarm Alarm No

Set to Live No Alarm Alarm No

Set to Live Alarm Alarm Yes (OFF) Read Note A

Set to Fail No Alarm Alarm No Read Note C

Set to Fail Alarm Alarm Yes (OFF) Read Note A

Set to FB No Alarm Alarm No

Set to FB Alarm Alarm Yes (OFF) Read Note A

Table Notes: A The 7951 will also raise a matching “ON” alarm if one does not already exist in the Historical Alarm Log.

This is normal and allows the system alarm to be cleared in the normal manner.

B The 7951 will raise a matching “OFF” alarm if the Audit Alarm Suppression Control setting is then changed to “No Alarm”. This is matching alarm is normal and allows the system alarm to be cleared in the normal manner.


Page 8.24 7951 2510 (Ch08/BC)

(Table Notes continued…)

C The 7951 will raise an ordinary Live INPUT alarm with an “ON” flag.

D The 7951 will raise an ordinary Live INPUT alarm with an “OFF” flag. This alarm can be cleared in the normal manner.

E Table 8.11 shows what happens when changes are made to the Audit Alarm Suppression Control attribute setting without changing the value or (value) status.

Table 8.11: Logic for determining if an alarm is generated when the “Alarm” or “No “Alarm” setting is changed

Value Status

Attribute: Alarm (Before)

Attribute: Alarm (After)

Alarm Raised?

Set No Alarm Alarm Yes (ON)

Set Alarm No Alarm Yes (OFF)

Fail No Alarm Alarm No

Fail Alarm No Alarm No

FB No Alarm Alarm No

FB Alarm No Alarm No

Live No Alarm Alarm No

Live Alarm No Alarm No

F Status changes that are not possible: “FB to Fail” and “Fail to FB”.

G A “USER” classed event is generated for all user initiated changes to the “No Alarm” or “Alarm” setting. Table 8.12 shows if an event will appear in the Historical Event Log when a user makes changes to the Audit Alarm Suppression Control setting without changing the value or value status.

Table 8.12: Logic for determining if an event is generated when the “Alarm” or “No alarm” setting is changed

Value Status

Audit Event Control Setting

Audit Alarm Ctrl Setting (Before)

Audit Alarm Ctrl Setting (After)


(Any) Audit No Alarm Alarm Yes

(Any) Audit Alarm No Alarm Yes

(Any) No Audit No Alarm Alarm No

(Any) No Audit Alarm No Alarm No

Chapter 9 Additional facilities

7951 2510 (Ch09/DC) Page 9.1

9. Additional facilities

9.1 Feature: Archiving 9.1.1 Introduction

The 7951 can perform data logging to generate historical records – archives - of parameter data. The archived data can be retrieved on-demand, and displayed within the menu system. It can also be printed out as a report and retrieved by MODBUS (protocol) networked devices.

Values from user-selected parameters can be statistically prepared (e.g. average, maximum, etc.) according to user requirements. Statistical results are recorded at intervals that are defined by the type of data logging. Each logging type has a separate archive with a 20-parameter capacity and the ability to keep statistics.

There are five types of data logging available:

1. IntervalStatistical results are automatically recorded in an “Interval Log” archive at a user-selected time-span. An interval can be as short as a 7951 machine cycle or as long as twelve hours. A user-selected date and time marks the start of the very first interval.

2. DailyStatistical results are automatically recorded in a “Daily Log” archive at the same time each day (i.e. 24-hour intervals). A user-selected date and time marks the start of the very first 24-hour period.

3. ManualStatistical results are recorded in a “Manual Log” archive only when triggered manually from the front panel or over serial communications. The beginning of this variable time-span occurs on enabling this type of data logging.

4. AlarmStatistical results are recorded in an “Alarm Snapshot Log” archive whenever an alarm is raised or is removed. (This is separate from the Alarm History log). The beginning of this variable time-span occurs on enabling this type of data logging.

5. Batch TransactionBatching data is automatically recorded in a “batch” archive every time a transaction is completed. This type of archiving does not need any configuring apart from adjustments to the archive size. Chapter 18 is dedicated to Batching.

Note that the “Statistical information” section (starting on page 9.2) and “configuring details” section (starting on page 9.8) do not apply to batch transaction archiving.

All the types can operate in parallel if required.

The size of an archive is finite but flexible enough to allow re-sizing by hand. Re-sizing actions cause all previously recorded values to be lost forever and should be done prior to data logging commencing.

Archives can be selectively viewed on screen and printed out as a report. Printouts of reports can also occur automatically after new statistical results have been archived. Associated parameters (database locations) can be manipulated or retrieved by MODBUS networked device.


Page 9.2 7951 2510 (Ch09/DC)

9.1.2 Statistical Information The following statistical options are available:

1. AverageThis calculates the average of a parameter value sampled every 7951 machine cycle. The resulting average is ready for whenever it is to be recorded to an archive.

2. DifferenceThis calculates the difference between the latest sampled parameter value and the result that was last copied to an archive. A result is ready for whenever it is to be recorded to an archive.

3. MaximumThis largest sampled parameter value, since that last archived statistic, is copied to an archive.

4. MinimumThis smallest sampled parameter value, since that last archived statistic, is copied to an archive.

5. NoneThis latest sampled parameter value is copied to an archive.

9.1.3 Analysis of an archive

This section explains:

Archive space and how it can change. How new statistical data is added to an archive.

Archive space, and how it changes Each archive has a default amount of memory space in the 7951. The initial amount is the same for each archive. Dimensions for archive memory space are in terms of depth and width.

Depth corresponds to the quantity of parameter values that can be kept.

Width corresponds to the total number of bytes required to store a single value from every nominated parameter (See Table 9.1).

Table 9.1: Bytes Required for all Database Location Types

Width(bytes) Data Type

1 Selection code for an option descriptor in a multiple-choice list

4 A database location without a status attribute (i.e. Set or Free) where the value (e.g. 1.25) is automatically generated by a measurement task. This does not include totals.

5 A data location with a status attribute (i.e. Set or Free) where the value (e.g. 1.25) may be generated by a measurement task.

8 Totals only. For example, Indicated Volume Flow Total 16 Dates and/or times. 21 Text only.

Available memory space for increasing the size of an archive can be viewed by pressing the PRINT MENUbutton and then selecting the menu: <“Archives”>/<“Re-size archives”>/<“Spare arch. memory”>.

It is very important to carefully plan the set-up of all archive space before data logging commences. Otherwise, be prepared for inevitable data loss if making changes or setting up other archives at a later stage.


7951 2510 (Ch09/DC) Page 9.3

Archive space can be change as follows:

Action Effects on associated archive Extent of data loss

Parameter added to nomination list Width increases. Depth decreases to compensate. Associated archive

Parameter removed from list. Width decreases. Depth increases to compensate. Associated archive

Space increase granted Depth increases. All archives

This is best illustrated in the following sequence of diagrams involving one archive:

Parameter 1Statistic entry 1

Statistic entry 3Statistic entry 2

Statistic entry 7:: :

Depth = 8

(1) Archive with an initial depth of 8 anda list with 1 defined parameter:-

The last available record




Parameter 2

:

Depth = 5

(2) Archive after adding another parameter:-

The last available recordStatistic entry 8

Width=4

Parameter 1 = Line temperature

Width=4 Width=16

Parameter 2 = Time and date

Diagram notes:(a) Parameters shown here are defined with a data location number. An archive can have a maximum

of 20 parameters.(b) The width value of a parameter is dependent on the type of data location. It is not displayed.(c) Depth is affected by the total width of parameters. Depth will therefore vary from the example shown

here.




Parameter 2

: Depth=9

(3) Archive after requesting room to allow 9entries for each parameter.





Depth=9

(4) Archive after removingparameter 2 from list



Statistic entry 9

Width=20 Width=4

Adding new statistics to an archive

Several questions can be asked about adding new statistics to an archive…

Q1. How are they inserted? Q2. What happens when all records of statistic results are full?

The answers to these questions are provided in the examples that follow.


Page 9.4 7951 2510 (Ch09/DC)

(a) Fixed time-span data loggingThis is described with two sequences of diagrams.

Sequence 1: Archive is not full This shows what will happen when adding statistics to an empty archive. Notice how older statistics are pushed downwards.

T5T0

Parameter 114.55Statistic entry 1



Parameter 21.0132

:

Parameter 3(Not used)

:

Newest and oldest statisitic at present

The last possible record for a statisitc in this archive

T1 = 8s T2 = 8s T3 = 8s T4 = 8s

Record:(1)14.55(2)1.0132

Record:(1)14.50(2)1.0133

Record:(1)14.53(2)1.0130

1 secondsamples

Record:(1)?(2)?

(1) Archive state after 8 seconds

Fixed time-span of data logging and archiving Diagram notes:(a) "Interval" type data logging is shown

with an 8 second time-span. "Daily" type logging operates in the

same way except T1=24 hours, T2=24hours, etc.

(b) 1 sampled value taken every secondfrom each defined parameter.

(Assume cycle time is 1 second for this).

(c) Parameter 3 is not defined.

(d) Recorded values shown here are notthe result of a specific statisticalcalculation.

(e) T0 is the date and time that this datalogging first began.

(f) Data logging continues beyond T5 untildisabled.

Parameter 114.53

14.50

Statistic entry 1


Statistic entry 6:

14.55

: :

Parameter 21.0130

1.0133

:

1.0132


(Not used)

:

(Not used)

Neweststatisitic at

present

Oldest statisticat presentThe last possible

record for a statisitcin this archive



7951 2510 (Ch09/DC) Page 9.5

Sequence 2: Archive is full This shows what will happen when adding statistics to a full archive. Notice how the oldest statistics have to be lost to make space for new statistics.

T9T0T1 = 8s T2 = 8s T3 = 8s T4 = 8s

Record:(1)14.55(2)1.0132

Record:(1)14.50(2)1.0133

Record:(1)14.53(2)1.0130

1 secondsamples

Record:(1)14.51(2)1.0130

Fixed time-span data logging and archiving

T5 = 8s T6 = 8s T7 = 8s T8 = 8s

Record:(1)15.0(2)1.0129

Record:(1)15.1(2)1.0128

Record:(1)15.2(2)1.0127

Record:(1)?(2)?

Parameter 115.1

15.0

14.55

Statistic entry 1


Statistic entry 6:

14.51

: :

Parameter 21.0128

1.0129

1.0132

:

1.0130


(Not used)

(Not used)

:

(Not used)

Newest statistic at present

The last possiblerecord for a statisitcin this archive

Parameter 115.2

15.1

14.50

Statistic entry 1


Statistic entry 6:

15.0

: :

Parameter 21.0127

1.0128

1.0133

:

1.0129


(Not used)

:

(Not used)

14.55 isnow lost

The last possiblerecord for a statisitc



Diagram notes:(a) "Interval" type data logging is shown

with an 8 second time-span.







Oldest statisitic at present

1.0132 isnow lost


Page 9.6 7951 2510 (Ch09/DC)

(b) Variable time-span data logging This is described with two sequences of diagrams.

Sequence 1: Archive is not full This shows what will happen when adding statistics to an empty archive. Notice how older statistics are pushed downwards.

T4T0

Parameter 114.55Statistic entry 1



Parameter 21.0132

:


:

Newest and oldest statisitic at present

The last possible record for a statisitc with this archive

T1 = 8s T2 = 16s T3 = ?s

Record:(1)14.55(2)1.0132

Record:(1)14.50(2)1.0133

1 secondsamples

Record:(1)?(2)?


Variable time-span data logging and archiving Diagram notes:(a) "Manual" or "Alarm" type data logging is

shown here with two completed time-spans. Third time-span is unknown untilan alarm is raised (or cleared) orlogging is next triggered manually by auser.





(e) T0 is when this data logging first began.


Parameter 114.50

14.55

Statistic entry 1



Parameter 21.0133

1.0132

:


(Not used)

:

Neweststatisitic at

present

Oldest statisticat presentThe last possible

record for a statisitcin this archive



7951 2510 (Ch09/DC) Page 9.7

Sequence 2: Archive is full This shows what will happen when adding statistics to a full archive. Notice how the oldest statistics have to be lost to make space for new statistics.

T9T0T1 = 6s T2= 7s T3 = 9s T4 =

5s

Record:(1)14.55(2)1.0132

Record:(1)14.50(2)1.0133

Record:(1)14.53(2)1.0130

1 secondsamples

Record:(1)14.51(2)1.0130

Variable time-span data logging and archiving

T5 = 8s T6 = 12s T7 = 8s T8 = ?s

Record:(1)15.0(2)1.0129

Record:(1)15.1(2)1.0128

Record:(1)15.2(2)1.0127

Record:(1)?(2)?

Parameter 115.1

15.0

14.55

Statistic entry 1


Statistic entry 6:

14.51

: :

Parameter 21.0128

1.0129

1.0132

:

1.0130


(Not used)

(Not used)

:

(Not used)

Newest statisitic at present


Parameter 115.2

15.1

14.50

Statistic entry 1


Statistic entry 6:

15.0

: :

Parameter 21.0127

1.0128

1.0133

:

1.0129


(Not used)

(Not used)

:

(Not used)

14.55 isnow lost



Diagram notes:(a) "Alarm" and "Manual" type data logging

are both represented with multiplevariable time-spans.






(f) Data logging to archive continuesbeyond T9 until disabled.

Oldest statisitic at present

1.0132 isnow lost



Page 9.8 7951 2510 (Ch09/DC)

9.1.4 Configuration details

Use the following table to find the instructions for configuring an archiving activity. It is advisable to try out an example before embarking on the configuration task.

Configuration task 1st. Page

Interval Archiving 9.9 Daily Archiving 9.10 Manual Archiving 9.11 Alarm (snapshot) Archiving 9.12 Re-sizing of archives 9.13

Note: Batch archiving does not require any configuring because it is automatically ready for any transactions that take place. Only re-sizing of the archive needs to considered, as guided in Section 9.1.3.


7951 2510 (Ch09/DC) Page 9.9

Configuration task: “Interval logging” Objectives: (i) Set-up a parameter list, (ii) ‘Set’ a start date/time, (iii) ‘Set’ a fixed interval and (iv) enable this data logging type.

Instructions: 1. Before proceeding, ensure that you have a list of parameters and their database location IDs 1. The

identification numbers are important because they will be input to identify parameters to be archived.

2. Press the PRINT-MENU button

3. Navigate to this menu: <“Archives”>/<“Configure logs”>/<“Interval log”>

4. Nominate the parameters to be archived

(a) Browse through the “Configure list” sub-menu to locate the ‘pointer’ and ‘action’ parameters.

(b) Starting with the first entry, program in a location ID and then select a statistical (action) function. (See Table 9.2 for further guidance)

(c) Repeat (4b) with the next entry until all parameters have been nominated.

5. Work through the remaining configuration parameters as guided in Table 9.3.

Table 9.2: First Entry Configuration Parameters

Parameters *(as displayed) Purpose

Int list loc 1 Nominate ‘parameter 1’ with a database location ID Int list action 1 Choose a statistical/non-statistical function to be applied to all values sampled from

‘parameter 1’. (Page 9.2 has a summary of the various supported functions)

* Abbreviations: “Int” = Interval, “loc” = location

Table 9.3: Configuration Parameter Checklist of Interval Archiving

Parameters *(as displayed) Purpose

Interval start time ‘Set’ the date and time for start of the first interval period. Interval time Select the interval frequency. Interval log/print Options:

(1) “Disabled” – deactivate data logging type / already deactivated (2) “Log data only” - activate data logging type but do not print-out a report after archiving (3) “Log and print data” – activate data logging type and print-out a report after archiving *

* Requires a serial port to be configured for connection to a printer or terminal. For further information, refer to Chapter 7

Interval Archiving Notes:

1. The interval type of data logging operates independently of the other types.

2. Intervals are always synchronised to the 7951 calendar clock. For example, a 10-second interval will first occur on the minute rollover and then re-occur every multiple of 10 seconds. An interval start time that is not divisible by the interval will effectively be delayed to the next multiple of the interval.

3. Some or all values could be lost if a power failure occurs while they are being logged. The data logging will re-synchronise to the calendar clock after the re-start.

1 The parameter location identification can be seen on-screen by navigating the parameter, and then pressing the a-button.


Page 9.10 7951 2510 (Ch09/DC)

Configuration task: “Daily” logging details Objectives:(i) Set-up a parameter list, (ii) ‘Set’ a start date/time and (iii) enable this data logging type




3. Navigate to this menu: <“Archives”>/<“Configure logs”>/<“Daily log”>


(4a) Browse through the “Configure list” sub-menu to locate the ‘pointer’ and ‘action’ parameters.

(4b) Starting with the first entry, program in a location ID and then select a statistical (action) function. (See Table 9.4 for further guidance)

(4c) Repeat step 4b with the next available list entry until all parameters have been nominated.

5. Work through the remaining configuration parameters as guided in Table 9.5Error! Reference source not found..

Table 9.4: Daily Archive - Configuration Parameters for First Entry of List

Parameter * (as displayed) Purpose of Parameter

Daily list loc 1 Nominate ‘parameter 1’ with a database location ID Daily list action 1 Choose a statistical/non-statistical function to be applied to all values sampled from


* Abbreviations: “Loc” = Location

Table 9.5: Daily Archive Configuration Parameters


Daily start time ‘Set’ the date and time for commencement of the first 24 hour period Daily report Options:

(3) “Disabled” – deactivate data logging type / already deactivated (4) “Log data only” - activate data logging type but do not print-out a report after archiving (3) “Log and print data” – activate data logging type and print-out a report after archiving *


Daily Archive Notes:

A Daily type data logging can operate independently of the others.

B A period that falls within an adjustment for daylight saving will be 24 +/- 1 hour.

C Some or all values could be lost if a power failure occurs while they are being logged. The data logging will re-synchronise to the calendar clock after the re-start.

2 The identification number of a parameter can be seen on-screen by navigating to the parameter and then pressing the ‘a’-key.


7951 2510 (Ch09/DC) Page 9.11

Configuration task: “Manual” logging details Objectives: (i) Set-up a parameter list and (ii) enable this data logging type




3. Navigate to this menu: <“Archives”>/<“Configure logs”>/<“Manual log”>


(4a) Browse through the “Configure list” sub-menu to locate the ‘pointer’ and ‘action’ parameterss.




Table 9.6: Manual Trigger Archive - Configuration Parameters for First Entry of List


Manual snap loc 1 Nominate ‘parameter 1’ with a database location ID Manual snap act 1 Choose a statistical/non-statistical function to be applied to all values sampled from


* Abbreviations: “snap” = snapshot, “loc” = location, “act” = action

Table 9.7: Manual Trigger Archive Configuration Parameters


Manual log/print Options: (1) “Disabled” – deactivate data logging type / already deactivated (2) “Log data only” - activate data logging type but do not print-out a report after archiving (3) “Log and print data” – activate data logging type and print-out a report after archiving *


Manual Trigger Archive Notes:

A The trigger for manual type data logging is activated by selecting a soft-command at the parameter with “Trigger manual log” as the parameter label. It is found under: <“Archives”>/<“Trigger manual log”>.

B Manual type data logging operates independently of the others.

C Some or all values could be lost if a power failure occurs while they are being logged. The data logging will re-synchronise to the calendar clock after the re-start.

3 The parameter identification number can be seen on-screen by navigating to the parameter, and then pressing the a button.


Page 9.12 7951 2510 (Ch09/DC)

Configuration task: “Alarm” (snapshot) logging details

Objectives: (i) Set-up a parameter list and (ii) enable this data logging type




3. Navigate to this menu: <“Archives”>/<“Configure logs”>/<“Manual log”>


(4a) Browse through the “Configure list” sub-menu to locate the ‘pointer’ and ‘action’ parameters.




Table 9.8: Alarm Triggered Archive - Configuration Parameters for First Entry of List

Parameter *(as displayed) Purpose of Parameter

Alarm snap loc 1 Nominate ‘parameter 1’ with a database location ID Alarm snap action 1 Choose a statistical/non-statistical function to be applied to all values sampled from


* Abbreviations: “snap” = snapshot, “loc” = location

Table 9.9: Alarm Triggered Archive Configuration Parameters


Log/print on alarm Options: (1) “Disabled” – deactivate data logging type / already deactivated (2) “Log data only” - activate data logging type but do not print-out a report after archiving (3) “Log and print data” – activate data logging type and print-out a report after archiving *


Alarm-Trigger Archive Notes:

A Alarm type data logging can operate independently of the others.

B Some or all values could be lost if a power failure occurs while they are being logged. The data logging will re-synchronise to the calendar clock after the re-start.

4 The identification number of a parameter can be seen on-screen by navigating to the parameter and then pressing the ‘a’-key.


7951 2510 (Ch09/DC) Page 9.13

9.1.5 Re-sizing Archive Space

Important notices! 1. Adding a parameter to a data logging list causes all recorded statistics to be immediately

lost from the associated target archive. Other archives are not affected by this.

2. Removing a parameter from a data logging list causes all recorded data to be immediately lost from the associated target archive. Other archives are not affected by this.

3. Increasing or decreasing space will result in all recorded data being lost from all archives.

Re-size Instructions: 1. Press the PRINT-MENU button

2. Navigate to this menu: <“Archives”>/<“Re-size archives”>

3. Check how much spare archive memory is available

Note: If the spare archive memory is reported as 0 bytes and archiving has not been in use, format the archives and then re-check the reported value

4. Re-size archives according to your requirements

The following are ‘re-size’ menus:-

(1) “Alarm log” – Alarm Trigger Archive re-sizing

(2) “Manual log” – Manual Trigger Archive re-sizing

(3) “Daily log” – Daily Archive resizing

(4) “Interval log” – Interval Archive resizing

(5) “Transactions log” – Batch Archive re-sizing

Each ‘re-size’ menu features two parameters. One parameter is for requesting an increase or decrease to the depth – i.e. the maximum number of values per parameter that can be presently stored in the associated archive. The other parameter shows the maximum number allowed at present.

To request more space for an archive:

(4a) ‘Set’ a new value in the appropriate ‘request’ parameter

(4b) Confirm the request for more space by selecting the "Format” soft-command (option descriptor) through the parameter with “Format all archives”.

Warning! Increasing or decreasing space will cause all recorded values to be lost from allarchives. Use the ‘max snaphot’ parameter to check on the result of a request.


Page 9.14 7951 2510 (Ch09/DC)

9.1.6 Operation details (Reporting) Operations involve selective viewing and printing out of the archives.

Viewing Archives Recorded values can be viewed on the 7951 display. No configuration is required for this feature. Follow the self-contained instructions that are provided below.

How to view the Interval Archive

1. Navigate to this menu: <“Archives”>/<”View / print logs”>/<”Interval trig log”>

2. Find out if data has been recorded in the archive by selecting the “Num snaps stored” menu option. The parameter shows how many values (per parameter) are available from previous elapsed intervals.

3. There are parameters (database locations) for displaying a previously recorded value for every listed (nominated) parameter. For example, the value of the first nominated parameter is found in the “Intvl snap value 1” parameter location.

By default, the most recently recorded values from the last interval can be seen. The “Select snapshot” menu option is for selecting another elapsed interval. For example, snapshot ‘1’ is for showing the oldest interval of recorded values. Selecting a ‘snapshot’ that does not yet exist will always cause all the most recent recorded values to be selected and then displayed.

4. The date and time, of when the presently displayed statistics were recorded, can be seen by selecting “View snapshot time” option.

How to view the Daily Archive

1. Navigate to this menu: <“Archives”>/<”View / print logs”>/<”Daily log”>

2. Find out if data has been recorded in the archive by selecting the “Num snaps stored” menu option. The parameter shows how many values (per parameter) are available from previous 24-hour periods.

3. There are parameters (database locations) for displaying a previously recorded value for every listed (nominated) parameter. For example, the value of the first nominated parameter is found in the “Daily snap value 1” parameter.

By default, only the most recently recorded values from the previous 24-hour period can be seen. Use the “Select snapshot” menu option to select another 24 hour period. For example, snapshot ‘1’ is for showing the very first 24-hour period of recorded values. Selecting a snapshot (i.e. 24-hour period) that does not yet exist will always cause all the most recent recorded values to be selected and then displayed.

4. The date and time, of when the presently displayed statistics were recorded, can be seen by selecting “View snapshot time” option.

How to view the Manual Trigger Archive

1. Navigate to this menu: <“Archives”>/<”View / print logs”>/<”Manual log”>

2. Find out if data has been recorded in the archive by selecting the “Num snaps stored” menu option. The parameter shows how many recorded values (per parameter) are available.

3. There are menu areas for viewing previously recorded values for each listed parameter. Look for the numerous “Snap item value” sub-menus. By default, only the most recently recorded values from the last trigger can be seen. Use the “Select snapshot” menu option to select and display recorded values from previous triggers. For example, edit a value of 1 to retrieve the oldest snapshot. Selecting a snapshot that does not yet exist will cause all of the most recent recorded statistics to be re-displayed.

4. The date and time, of when the presently displayed statistics were recorded, can be seen by selecting “View snapshot time” menu option.


7951 2510 (Ch09/DC) Page 9.15

How to view the Alarm Trigger Archive

1. Navigate to this menu: <“Archives”>/<“View / print logs”>/<“Alarm log”>

2. Find out if data has been recorded in the archive by selecting the “Num snaps stored” menu option. The parameter shows how many recorded values (per parameter) are available.

3. There are a number of parameters for viewing previously recorded values for all listed parameters. Look for the numerous “Snap item value” sub-menus.

By default, only the recorded values since the last alarm can be seen. The “Select snapshot” menu option is for selecting and displaying recorded values from previous new alarm occurrences. For example, editing a value of ‘1’ will select the oldest set of values. Selecting a snapshot that does not yet exist will always cause the most recent recorded values to be selected and then displayed.

4. The date and time, of when the presently displayed values were recorded, can be seen by selecting “View snapshot time” option.

How to view the Batch Archive

1. Navigate to this menu: <“Archives”>/<“View / print logs”>/<“Transaction log”>

2. Find out if data has been recorded in the archive by selecting the <“Num snaps stored”> menu option. The parameter shows how many batch transactions were recorded.

3. There are a number of parameters for viewing previously recorded values for all listed parameters. Look for the numerous “Snap item value” sub-menus.

By default, recorded values since the last alarm can be seen. The “Select snapshot” menu option is for selecting and displaying recorded values from previous batch transactions. For example, editing a value of ‘1’ will select the oldest set of values. Selecting a snapshot that does not yet exist will always cause the most recent recorded statistics to be selected and then displayed


Page 9.16 7951 2510 (Ch09/DC)

Printing Archives (through a configured serial port)

Archives can printed-out in several ways:

1. Method: On-demand (1a) From outside the <“Archives”> menu

This feature requires no configuration. To activate, press the PRINT-MENU button, and then select the “Print report” menu option. Now choose a report by selecting from the multiple-choice of options.

Option (as displayed) Purpose of option

Interval log Printout the ‘Interval’ archive as a report. Daily log Printout the ‘Daily’ archive as a report.

Manual log Printout ‘Manual’ archive as a report. Alarm log Printout ‘Alarm’ (Snapshot) archive as a report.

(1b) From inside the <“Archives”> menu

This feature requires no configuration. To activate, press the PRINT-MENU button and then the follow instructions.

Instructions:1. Navigate to this menu: <“Archives”>/<“View / print logs”>

2. Select a menu that is name-associated with the archive

3. Select the “Print snapshot” menu option

4. Select the “Print” soft-command option (value)

2. Method: Automatic Printed Report Archiving can be configured to automatically printout a report whenever data is archived.

Interval archive instructions:

1. Navigate to this menu: <“Archives”>/<“Configure logs”>/<“Interval log”>/<”Enable”>

2. Select the “Log and print data” option

Daily archive instructions:

1. Navigate to this menu: <“Archives”>/<“Configure logs”>/<“Daily log”>/<”Enable”>


Manual archive instructions:

1. Navigate to this menu: <“Archives”>/<“Configure logs”>/<“Manual log”>/<”Enable”>


Alarm archive instructions:

1. Navigate to this menu: <“Archives”>/<“Configure logs”>/<“Alarm log”>/<”Enable”>


Batch archive instructions:

1. Navigate to this menu: <“Archives”>/<“Configure logs”>/<“Transaction log”>/<”Enable”>


All methods require a Serial Communications Port to be set-up for printing. Printouts are transmitted through the serial port that is configured exclusively for connection to a printer.


7951 2510 (Ch09/DC) Page 9.17

9.1.7 Guided examples of archiving

Guided Example 1

Objective: (i) Set-up 7951 to record the average of line pressure measurements on a daily basis

This guided example involves configuring the “Daily log” archive to record (snapshot) the average of all pressure readings during a 24-hour period. It is assumed that the measurement task is already set-up.

Instructions:

1. Add the parameter to the “Daily log” archive list

(1a) Press the PRINT-MENU button

(1b) Navigate to this menu: <“Archives”>/<“Configure logs”>/<“Daily log”>/<“Configure list”>/<“Entry 1”>

(1c) Select the “Pointer” menu option – this displays a parameter with “Daily list loc 1”

(1d) Press the b button and then type in the database location ID for the pressure parameter

(1e) Confirm the edited location ID by pressing the ENTER button

(1f) Select the <“Action”> menu and then change the parameter option selection to “Averaging”

2. ‘Set’ an initial date and time

(2a) Navigate to this menu: <“Archives”>/<“Configure logs”>/<“Daily log”>/<“start time”>(2b) Press the b button and then edit a date and time for the commencement of the first 24-hour period

Notes: The 7951 date and time is displayed within menu system. Look inside this menu: <”Time”> A date of ‘zero’ is the same as specifying the present calendar date. A time of ‘zero’ is the same as specifying the present time.

3. Activate the data logging activity

(3a) Select menu: <“Archives”>/<“Configure logs”>/<“Daily log”>/<“Enable / Disable”>(3b) Choose an option as guided in the table


Log data only Data copied into the “Daily log” archive. No printed report following archive Log and print data Data copied into the “Daily log” archive. Print a report following archive. *

* A serial port should be configured for connection to a ‘printer’

4. Check on the data logging after 24 hours

Results are best viewed on a connected printer or a PC running a terminal emulation program. Alternatively, results can be viewed within the menu system.

(4a) Select the menu: <“Archives”>/<“View / print logs”>/<“Daily log”>

(4b) Select various parameters…

Parameter (as displayed) Purpose

Num daily snapshots The number of snapshots per parameter inside the “Daily log” archive. Daily snap, 0=latest View selection: 0 = recent snap, 1 = oldest snap, 2 = 2nd oldest snap, etc.Daily snap value 1 Selected view of a value from the parameter listed under “Entry 1”.

Daily snapshot time Shows the date and time of the last daily snapshot.


Page 9.18 7951 2510 (Ch09/DC)

9.2 Feature: PID Control Proportional-Integral-Derivative (PID) is a control algorithm for efficiently attaining and then maintaining a LIVE measurement parameter at a user-supplied target (or ‘set-point’) value. PID control is available for controlling one measurement parameter.

WARNING! EXPERT KNOWLEDGE OF PID IS ESSENTIAL TO MAKE USE OF THIS FEATURE

9.2.1 Overview

Closed-loop PID ControlThe implemented PID algorithm will continuously check on the difference between a target (‘set-point’) measurement value and the latest LIVE value of a nominated measurement. Whenever the difference is unacceptable, an adjustment – to narrow the difference - is derived from a three-term equation, as seen below.

A calculated adjustment value – or PID output value - is checked against any enabled safeguards before being made available in a database location. Once the PID output value is freely available, it can be transmitted to an external system through any analogue output. That action should result a process change to narrow the difference. This routine is repeated every cycle until the difference is within acceptable limits.

m i K e i T K e k KT

e i e ic id

k

i

* * * 10

ProportionalTerm

IntegralTerm

DeriviativeTerm

Where:

m i = Control output (for steering measurement towards a set-point) {Parameter: <“PID Output”>}

Kc = Proportional gain factor {Parameter: <“PID Gain”>}

Ki = Integral time constant (‘Reset’ rate) {Parameter: <“PID Integral act”>}

Kd = Derivative time constant {Parameter: <“PID Derivative act”>}

e i = Difference between set-point and measurement (i.e. the ‘error’) at cycle i{No Parameter}

e i 1 = Difference between set-point and measurement (i.e. the ‘error’) from previous cycle {No Parameter}

e k = The error over k cycles for 0 k i{No Parameter}

T = Elapsed time since measurement value last sampled for PID algorithm {No Parameter}

Notes:(1) Variables Kc , Ki and Kd can be edited through pages within the 7951 menu system.

(2) In practice, the first order difference term, (e(i) - e(i-1)), is very susceptible to noise problems. In most practical systems this term is replaced by the more stable, higher order equation: e = ( e(i) + 3*e(i-1) - 3*e(i-2) - e(i-3) ) / 6


7951 2510 (Ch09/DC) Page 9.19

Open-loop PID ControlWith this method, the aim is for the PID output value itself to be driven towards a user-supplied target (set-point) output value. The measurement ‘set-point’ has no purpose.

Whenever there is a calculated difference, an adjustment – to narrow the difference - is derived from the three-term equation seen earlier. However, the calculated ‘error’ terms are based on the difference between the “LIVE” PID output value and a “SET” target (user) PID output value.

The calculated adjustment value – PID output value - is checked against two safeguards before being made available in a database location. Once the PID output value is freely available, it can be transmitted to an external system through any analogue output. That action should result a process change to gradually narrow the difference. This routine is repeated every cycle until the difference is within acceptable limits.

9.2.2 Configuration details Instructions:1. Set-up the “LIVE” measurement that is to be controlled

All the configuration reference pages for measurements are located in Chapter 11. Ensure that the location identification number 5 of the measurement (to be controlled) is noted

2. Set-up PID control Review schematic (Figure 9.2.1) in conjunction with the associated parameters (Table 9.10) Navigate to this menu: <”Configure”>/<”PID Control”> and then work through all the associated

parameters, setting values and selecting options as necessary. Check on the idle system time to see if the cycle time needs to be increased. [MENU: <”Time”>]

3. Configure a live analogue output to transmit a PID output value

During every machine cycle, the analogue output will need to transmit a PID output value to whatever external system can initiate a process change (e.g. a valve controller increasing flow).

The PID output value is either: An adjustment for the “LIVE” measurement to reach a target (set-point) measurement value, or An adjustment for the PID output value itself to reach a target (set-point) value, also indirectly affecting

the “LIVE” measurement. [Note: The measurement set-point is not used in this case]

A guide to the analogue output parameters and settings is listed in Table 9.11 (on page 9.20)

Figure 9.2.1: PID Control - Schematic of Blocks and Parameters

Calculate'Error'

3

PIDAlgorithm

5 6 7SETPOINT

(for measurement)

"LIVE" MEASUREMENT

4

ARWLimit

Check8 9

10 11

CheckRamp Limit

13 14

16

PIDOutput

"LIVE"AdjustmentValue (%)

mA Output15OR12

SETPOINT(for PID output)

Status checkdecides the

set-point used

PIDOutput

12

5 This number can be found by examining the ‘.man’ text file that is present on the media of our FC-Config PC tool.

The ‘.man’ file is unique for every software release. Contact us if you require a copy of the file and/or FC-Config. Alternatively, locate the data page within the menu system, and then use the a-button to toggle the display of the number on/off.


Page 9.20 7951 2510 (Ch09/DC)

Table 9.10: PID Control Parameters

Index Parameter(as displayed) Default Setting Notes?

- PID Enable “Disable” 1 PID Setpoint ptr (“PID Setpoint”) A 2 PID Setpoint 0.0 (A) 3 PID Input ptr 0000 (“Off”) B 4 PID Error type “Single error” C 5 PID Gain 0.06 PID Integral act 0.07 PID Deriviative act 0.08 PID Range max 0.09 PID Range min 0.010 PID ARW “Disable” D 11 PID ARW HI limit 0.0 (%) (D) 12 PID ARW LO limit 0.0 (%) (D) 13 PID Ramp limit “Ramp limit off” E 14 PID Ramp Gradient 5.0 (%) (E) 15 PID Output * 0.0 F:1, G

16 PID User Output * 0.0 F:2, G * shows data that can be “Live” or “Set”

Table 9.11: Analogue Output '1' Parameters (Guide for PID Control Set-up)

Parameter(as displayed)

Example Value or Option Setting Comments

mA output 1 ptr list “User” Essential option mA 1 param val @100% (<”PID Range max”> Value) See Table 9.10

mA 1 param val @0% (<”PID Range min”> Value) See Table 9.10mA output 1 type (4-20mA or 0-20mA) Select suitable mA range

mA output 1 source (<”PID Output”>) ID for <”PID Output”> mA output 1 value * (LIVE Value) Values from <”PID Output”>

Analogue Output ‘1’ has been used here as a guide to setting-up

Notes: (for Table 9.10) A By default, this configuration parameter is usually programmed with the database location ID of the parameter

<“PID Setpoint”>. However, any database location with a floating-point value could be identified - programmed in - as the parameter supplying the set-point (target) value. An input alarm is raised if the ‘value’ of the identified ‘set-point’ parameter is not a floating-point value. PID control is then temporarily deactivated until the alarm is clearable when a more suitable parameter is identified.

B This configuration parameter must be programmed with the database location ID of the measurement parameter that is to be controlled. It must be a parameter with a floating-point value. An input alarm is raised if the ‘value’ attribute of the measurement parameter is not a floating-point data type. PID is then temporarily deactivated until the alarm is clearable when a suitable parameter is identified.


7951 2510 (Ch09/DC) Page 9.21

(Notes continued…)

C The “Simple Error” option will calculate the ‘error’ as simply the difference between the setpoint value and the measurement value. However, the “Complex Error” option will provide a more stable ‘error’ value. The error is derived from the following expression: e = (e(i) + 3*e(i-1) - 3*e(i-2) - e(i-3) ) / 6

D Safeguard feature. See Section 9.2.4 on page 9.22.

E Safeguard feature. See Section 9.2.3 on page 9.21.

F:1 For the closed-loop method you must change the status of <”PID Output”> and <”PID User Output”> to both be “Live”. Calculated adjustment values will then be displayed by both parameters.

F:2 For the open-loop method you need to SET a value for the <”PID User Output”> parameter. The status of the <”PID Output”> parameter must be “LIVE”.

G Set-up any analogue output to transmit a value of the <”PID Output”> parameter. This database location ID is 1288. Configure the analogue output to utilise the ‘user parameter’ option. Refer to Chapter 11 for applicable configuration reference pages. Analogue output connections are as guided in Chapter 2.

9.2.3 Ramp-limit Safeguard

Many systems implement a limiter on the maximum rate of change to the PID output value. This has a similar effect to an engine rev-limiting device. However, this PID safeguard prevents physical devices from being damaged through unnecessary adjustments.

The ramp-limit is specified in degrees, representing the angle the output makes with the horizontal on a graph. The time axis resolution is therefore critical to the significance of this parameter. A limit of zero degrees would make output ramping impossible and a limit of 90 degrees or greater would allow maximum ramping.

With the open-loop PID control method, the ramp-limit checks are mandatory and are applied every cycle. However, programming a zero degree angle will inhibit this safeguard.

Figure 9.2.2: Ramp-Limit safeguard illustration

PID

Oup

ut (%

)

X1

Y

X2Y

Ramp LimitGradient

PID Output(Tangent)

Xn

PID Output(Angle)

Y

Ramp Limit(Angle)

X2< Y

X1< Y Time


Page 9.22 7951 2510 (Ch09/DC)

9.2.4 Anti-Reset-Windup Safeguard

Practical systems stop the summation of error terms if the PID output value is outside a user-specified boundary. This limiting of the error summation is commonly referred to as Anti-reset-windup (ARW).

When ARW is enabled, ARW limiting is applied to every output value from the PID calculation before it is saved in the 7951 database. The ARW limit boundary is specified as a low and high percentage of the full-scale (maximum) PID output value.

With the open-loop PID control method, the ARW boundary checks are mandatory and are applied every cycle. However, a zero percent boundary will inhibit ARW limiting.

Figure 9.2.3 demonstrates ARW in action, complemented with example settings as shown in Table 9.12.

HIGH

LOW

AR

W B

ound

ary

TIME

PID

OU

TPU

T (%

)

0

100

Process change(e.g. Pump failure)

ARW is limiting output %(e.g. minimum flow)

Process change(e.g. pump fixed)

ARW is limiting output %(e.g. maximum flow)

HIGH

LOW

AR

W B

oundary

5

90

PID OUTPUT varyingas process changes

Figure 9.2.3: Anti-reset-windup (ARW) in action

Table 9.12: ARW Associated Parameters

Parameter ** (as displayed) Example Setting Comment

PID Range max 100.0 The maximum – full-scale - PID output value PID Range min 0.0 The minimum allowed PID output value

PID ARW “Enable” Activate ARW boundary checking PID ARW HI limit 100.0 (%) % of <PID max range> for upper ARW boundary PID ARW LO limit 0.0 (%) % of <PID max range> for lower ARW boundary

PID Output * (“Live” Value) “LIVE” Adjustment value (%) for the mA output

* shows data that can be “Live” or “Set” ** Parameters are located within this menu: <”Configure”>/<”PID control”>


7951 2510 (Ch09/DC) Page 9.23

9.3 Selecting units and data formats You can select the units which it displays the data, as well as the formats in which the data is displayed. You can choose the units and formats for:

Volume flow rate. Volume flow total. Standard volume flow rate. Standard volume flow total. Mass flow rate. Mass flow total. Density. Temperature. Pressure. ‘K’ factor. Time period. Kinematic viscosity. Base kinematic viscosity. Dynamic viscosity.

A full list of the units (metric and imperial) is given at the end of this chapter. Note that, if you change the units, the values are converted automatically to reflect the change.

9.4 Parameter Alarm Limits You can set limits for some parameters so that an alarm is generated if the limits are exceeded.

There are four types of limit:

High limit: The highest value that the parameter can have before an alarm is generated.

Low limit: The lowest value that the parameter can have before an alarm is generated.

Step limit: The greatest allowable step between successive values before an alarm is generated.

Comparison limit: The greatest allowable step between values from two or more channels without an alarm

The parameters, and the types of limit that you can set for them, are: Mass flow rate: high and low Gross volume flow rate: high and low Net volume flow rate: high and low Sediment and Water high and low Meter density: high, low and step Density ‘A’ & ‘B’ Comparison Base density high and low Meter temperature: high and low Meter pressure: high and low Prover Inlet temperature high and low Prover outlet pressure high and low Prover Inlet pressure high and low Prover outlet temperature high and low Alarm X and Y: high and low. Alarm ‘A’ and ‘B’ Comparison


Page 9.24 7951 2510 (Ch09/DC)

Indic. Std. volume flow rate: high and low Gross Std. volume flow rate: high and low Turbine frequency high Dynamic viscosity High, low and comparison Kinematic viscosity High and low

9.5 Fallback values and modes A fallback value is used as a temporary substitute for a parameter if a live input (i.e., the transducer, transmitter or wiring), which is normally used to calculate the parameter, should fail.

A fallback must have one of the following modes:

None The system uses whatever value is available for the parameter regardless of whether or not the live input has failed.

Last good value The system uses, for the parameter, the last value prior to failure.

Fixed value The system uses whatever fixed value you have specified for the fallback.

You can set fallback values for:

Metering density. Base density. Metering temperature. Prover inlet temperature. Prover outlet temperature. Prover inlet pressure. Prover outlet pressure. Metering pressure. Densitometer pressure. Sediment & Water percentage.

9.6 Units which the 7951 can display The 7951 can display data values with many different units of measurement, as listed in Table 9.13 on page 9.25. However, when communicating with other devices, the data is always sent using the base units.

In Table 9.13, the following definitions are used:

Base units The 7951 transmits all data in base units (when using a MODBUS link). Data values in the 7951 database are stored in base units for calculations.

Default units: Units which the 7951 displays unless you choose an alternative.

Other units: Units which you can choose instead of the default.

Note that many of the abbreviations used in the tables are defined in the glossary.


7951 2510 (Ch09/DC) Page 9.25

Table 9.13: Supported units of measurement

Parameter Category

Base units (Comms. &

Calculations) Default units (on-screen)

Other units available for on-screen (as displayed)

Temperature Deg. C Deg. C Deg. F Kelvin Ohms

Pressure bar abs bar abs

Pa abs psiakPa guage kg/cm2

KPa abs bar guage MPa guage

MPa abs Pa guage psig

Volume m3 m3

m3 x E3

ft3

barrelcc

m3 x E6

100ft3 gallon (UK) litres

in3

MM ft3

gallon (US)

Standard Volume Std m3 Std m3

Std m3 x E3

Std ft3

Std barrel Norm cc Norm m3 x E3

Norm ft3

Norm barrel Std cc

Std m3 x E6

Std 100ft3

Std gallon (UK) Norm litres Norm m3 x E6

Norm 100ft3

Norm gallon (UK) Std litres

Std. in3

Std MM ft3

Std gallon (US) Norm m3

Norm in3

Norm MM ft3

Norm gallon (US)

Mass (Total) kg kg tonne ozg

ktonne lb

Mtonne ton

Density kg/m3 kg/m3

tonnes/m3

oz/barrel lb/in3

lb/gallon (UK) tons/barrel g/cckg/cc

oz/in3

oz/gallon (UK) lb/ft3

lb/gallon (US) tons/gallon(UK) g/litrekg/litre

oz/ft3

oz/gallon (US) lb/barrel tons/ft3

tons/gallon (US) g/m3

kg/cm2

Base density kg/m3 kg/m3 As density

Time s (seconds) s (seconds) minus

hourms

day

Frequency Hz Hz kHzpulse m/s

pulse/ns pulse/s

pulse u/s pulse/min

‘K’ Factor pulse/m3 pulses/m3pulse/in3

litre/pulse ft3/pulse

pulse/ft3

m3/pulse pulse/cc

cc/pulsein3/pulse pulse/litre

Dynamic Viscosity cP cP

Pa.sReyn

kgf.s/m2

slug/fts Plbf.s/ft2

Kinematic Viscosity cSt cSt

mm2/sft2/s

cm2/s m2/s

Base Kinematic Viscosity cSt cSt

mm2/sin2/s

cm2/sft2/s

m2/s

Mass rate kg/hour kg/hour Mass units / time unitsVolume rate m3/hour m3/hour Volume units / time units

Standard volume rate m3/hour m3/hour Volume units / time units


Page 9.26 7951 2510 (Ch09/DC)

Chapter 10 Configuring by using Wizards

7951 2510 (Ch10/CE) Page 10.1

10. Configuring using Wizards

10.1 Introduction to WizardsWe recommend that you use software Wizards to configure the parameter for your installation. Wizards are easy to use facilities that will take a user through all the data locations and decisions that are required to satisfy the requirements of a measurement task.

There are individual wizards available for each measurement task. For example there is a “Pressure” Wizard for configuring line pressure and atmospheric pressure.

To fully configure a parameter, it is very likely that several measurement tasks are required and, therefore, several wizards will need to be used. It is often more efficient to use a “full set-up” wizard. This Wizardcan guide users through setting up more than measurement task.

Section 10.3 has a “Quick-view” guide (table) for finding out what Wizards are available and what can be achieved with them.

Section 10.4 features a special Wizard for selecting a standard for units of measurement.

10.2 Using WizardsAlthough wizards are easy to use, some preparation is still required. Use the following check-list to prepare.

Ensure that:

All physical connections to the rear panel have been completed.

If this is not the case, refer to Chapter 2 (Getting Started) and Chapter 3 (About the parameter) for details of supported connections.

Front panel keyboard buttons and the menu system are familiar.

Chapters 5 and 6 are provided to assist with this. It might be a good idea to bookmark the summary of buttons in Chapter 5 for quick reference.

Identification numbers of important result data are written down.

These numbers will be required for configuring facilities such as analogue outputs. There are two ways to find out data location numbers:

(1) Examine the “.man” file that is supplied on the FC-Config1 media, or

(2) Locate the data within the menu system and then press the a-button to display the unique identification number on line 4. (Pressing the a-button toggles the number display on or off.)

Calibration certificates (and supporting data sheets) for all field instrumentation are available.

There is a comprehensive list of all the parameter input and output connections that are being used and a list of the measurement tasks that are required.

1 Available on request.


Page 10.2 7951 2510 (Ch10/CE)

Starting a Wizard from the front panel is easy.


Step 1: Press the MAIN-MENU button.

Step 2: Use the DOWN-ARROW button to scroll through pages until the “Configure” option appears.

Step 3: Press the lettered-button that is alongside the “Configure” option.

Step 4: Press the a-button twice so that “Setup Wizard” appears on line one of the display. Do not worry about what line two is presently displaying.

Step 4: Press the b-button once to start the Wizard selection process.

Step 5: Use the DOWN-ARROW button to scroll through all available wizards (on line two).

Step 6: Press the ENTER button twice to select and then start a wizard that was named is on-screen.

After a Wizard is started, follow the prompts to supply the information it asks for, and then, if necessary, use Chapter 11 and the menu system to edit the resulting configuration to match your exact needs.

Wizard interactions involve these buttons:

a, b, c ,d buttons Answer a question (e.g. “Yes” or “No”) or used for normal data location editing

ENTER button Confirm a selection or edited setting (e.g. new value), move on to next prompt

< button Go back to a previous important decision prompt.

After completing a Wizard, the screen with “Setup Wizard” re-appears. Further Wizards can then be selected in the same way as before. Note that it is not necessary for the “None” option to be selected before proceeding to other 7951 work.


7951 2510 (Ch10/CE) Page 10.3

10.3 Quick-view Guide (Set-up Wizards)

Table 10.1: Wizards selection

Wizards Measurement Tasks Comments

Full Setup Multiple measurement tasks Skip the tasks that are not applicable.

Flow meter Frequency (Turbine Flow) ‘Meter factor’ and ‘K factor’

See Chapter 11 for measurement details

Flow rate Gross Volume flow rate Indicated Standard Volume flow rate Gross Standard Volume flow rate Nett Standard Volume flow rate Mass rate


Txdr density Density ‘A’ Density ‘B’ Prime Transducer Density


Base Density Base density (API or 4x5 Matrix Referral) See Chapter 11 for measurement details

Meter Density Meter Density See Chapter 11 for measurement details

Txdr viscosity Transducer Viscosity See Chapter 11 for measurement details

Referred viscosity Referred Viscosity See Chapter 11 for measurement details

Specific gravity Specific Gravity See Chapter 11 for measurement details

Temperature Meter temperature Density temperature ‘A’ Density temperature ‘B’


Pressure Metering-run Pressure See Chapter 11 for measurement details

Sediment & Water BSW Percentage See Chapter 11 for measurement details

Special calc. Special Equation Type 1 See Chapter 11 for measurement details

Analog outputs mA signal outputs See Chapter 11 for measurement details

Pulse outputs Pulse outputs See Chapter 11 for measurement details

Alarms User alarms Chapter 8 is about alarms.

Multi view Multi-view (Multi-view display button) See Chapter 11 for measurement details

Communications Printer Modbus Slave Modbus Master

Chapter 7 is a full guide to 7951 Communications

Prover Prover and Proving Details See Chapters 16A and 16B for proving support

PID setup PID Controls Refer to Chapter 9

Batch setup Batching transactions Refer to Chapter 18

HART inputs Live inputs from SMART type transmitters Chapter 17 is a full guide to HART support


Page 10.4 7951 2510 (Ch10/CE)

Strainer input Strainer input See Chapters 16A and 16B.

Retro batch calc Retrosepective batch calculation Refer to Chapter 18

Reset Full reset Use this with caution!!

Initialise Clear all user programming to defaults Use this with caution!!

10.4 Units Wizard Selection Follow these instructions to select a standard for the units of measurement:

Step 1: Press the MAIN-MENU button.

Step 2: Use the DOWN-ARROW button to scroll through pages until the “Configure” option appears.

Step 3: Press the lettered-button that is alongside the “Configure” option.

Step 4: Press the lettered-button that is alongside this description: “Units wizard”‘

Step 5: Press the b-button once to start the selection process.

Step 6: Use the DOWN-ARROW button to scroll through all available options (see map below).

Step 7: Press the ENTER button twice to select the standard that is named is on-screen.

"Imperial"

"Metric"

Choosing this will not do anything. Use scroll up/down keysto move through the wizard options.

Units wizard(Selection)

Choose option

Metric

Imperial

SI

Exit Wizard

"SI"

Figure 10.1: Units Wizard Selection

Chapter 11 Configuring without using Wizards

7951 2510 (Ch11/DD) Page 11.1

11. Configuring without using Wizards

11.1 What does this Chapter tell me? This chapter is a configuration reference for those who are reasonably experienced with configuring a 7951 computer. It is also useful for those who provide technical support.

It is primarily organised for a structured approach to configuring - the live inputs, the calculations and the live outputs - after the first power-on with 2510 software installed.

For those in a support role, a ‘quick-find’ index is provided. Use the index to find the reference pages required for configuring or trouble-shooting a measurement task.

If you are not experienced, return to Chapter 10 (Wizards) unless directed here by the manual, or by someone providing support.

Not all features are covered in this Chapter. For example, configuring for HART communications and for flowmeter proving is a complex task and therefore kept in separate chapters. There are additional features in Chapters 7, 8, 9, 17 and 18.

Quick-find Index ........................................... 11.2

A structured approach to configuring............ 11.3

Reference Page Conventions ...................... 11.5

Reference information .................................. 11.6+

Rounding Compliance Statement

Liquid Flow Computer software complies with the API standard for rounding down the floating-point values of live density and base density referral measurements. The rounding procedure is also applied to all inputs to the referral calculations (e.g. temperature) and auxiliary outputs from the referral calculations (e.g. CTL). Relevant sections in the standard are API 12.2 and API 11.1 VOL X.

By default, rounding is inactive. It can be activated for the next cycle by navigating to the <Rounding> configuration menu and then editing the multiple-choice option. When active, we recommend you change the displayed measurement units of associated parameters to metric units


Page 11.2 7951 2510 (Ch11/DD)

11.2 Quick-find Index Use Table 11.1 to quickly find the pages that are of interest.

Table 11.1: Quick-Find Index

Category Measurement Task 1st.Page

Analog Inputs (mA and RTD/PT100) 11.06 Digital (Status) Inputs 11.07 Live Inputs Pulse Inputs 11.08 Turbine/PD 11.09 Orifice ( P) 11.16

Flow MeteringSystem Coriolis 11.28

Totalising Metering-run Totals 11.31

‘Density Loop’ Fluid Temperature 11.33 ‘Viscosity Loop’ Fluid temperature 11.34 Temperature Meter Fluid Temperature 11.35 ‘Density Loop’ Pressure 11.36

Pressure Meter Pressure 11.37 Header Density 11.38 API referral (header base and base run) 11.44 4x5 referral (header base and base run) 11.45 Known fluid meter density (GPA, IUPAC, etc.) 11.46 Known fluid base density (GPA, IUPAC, etc.) 11.47 Specific gravity 11.48 Degrees API 11.48

Density Measurement

System

Special Equation 11.49 Header ‘viscosity loop’ density 11.50 Header viscosity 11.52

Viscosity Measurement

System Referred viscosity 11.55

BS&W Prime selected Header BS&W analyser channels 11.57

Percentages of oil (by volumes and mass) 11.59 Percentages of ‘water’ (by volumes & mass) 11.59 Net Oil/Water Net flow rates and totals (for oil and ‘water’) 11.65

Product detection system Interface Detection Product totals

11.74

Analog Outputs 11.73 Digital (Status) Outputs 11.77 Live Outputs Pulse Outputs 11.78

7951 Security

Passwords and security levels Security level fallback 11.79

Multi-view Multi-view display 11.81


7951 2510 (Ch11/DD) Page 11.3

11.3 A structured approach to configuring Preparation will help ensure that configuration work progresses smoothly. At this stage, it is expected that all the connections have already been made to the 7951 Flow Computer. If possible, check on this by asking the relevant authority. Familiarity with the front panel keyboard and menu system is also expected.

Work through the preparation and configuration stages that are listed below.

11.3.1 Preparation stage

1. Ensure that all of the information needed is at hand:

A plan of the pipeline layout.

A summary of instrumentation connected to the 7951 Flow Computer, providing inputs or expecting outputs. Include the type of logical connections made to the rear panel of the 7951 Flow Computer. (e.g. “a mA type pressure transmitter wired to analogue input 3”).

Calibration certificates of connected instrumentation.

Operational data (e.g. minimum and maximum flow rates).

A summary of core measurements to be set-up (e.g. flow rates, flow totals, density, etc.)

(It may be useful to look in Chapter 3 and browse through this Chapter).

Identification numbers of data that is important

(This is for configuring multi-view and analog outputs that can require the input of a location number).

A plan of what is required from additional features (e.g. Batching, Archiving, etc.)

(It may be useful to look in Chapter 9 and browse through this Chapter).

2. Read the information on conventions used.

3. Browse through the rest of this chapter and see how the reference pages are organised.

11.3.2 Configuration stage

1. Get the 7951 Flow Computer into the Programmer security level. (Turn the security key to the far right or type in the ‘Programmer’ password to change security level).

2. Set the display contrast, display formats, and the system cycle time. The display contrast may be quite dim when first powering-on the 7951 Flow Computer with new

software. Look in the <“configure”>/<“Additional features”> menu for the appropriate menu, and then change the setting to suit the environment.

Display formats are important when decimal places of results are critical. They are categorised under general headings (e.g. temperature, pressure, etc.). Look in the menu <“configure”>/<“Additional features”> for the appropriate menu, and then change the settings if the defaults are not appropriate. Units of measurement can be changed also.

The machine cycle time is dependent on how much work the 7951 Flow Computer is performing. Examine the idle cycle time indicator in the <“Health Check”> menu to see if the cycle time needs to be increased, or decreased.

DO NOT CHANGE ANY SETTINGS UNDER THE CALIBRATION MENUS. SETTINGS ARE MADE BY SPECIALIST CALIBRATION EQUIPMENT AT THE FACTORY.


Page 11.4 7951 2510 (Ch11/DD)

3. Configure the live (transmitter) inputs to get raw readings from instrumentation. HART Inputs All reference information is in Chapter 17. Analog Inputs Turn to page 11.6

4. Set-up the calculation processes. Pulse inputs, flowmeter details, flow rates, sediment & water, flow totals, temperature, pressure, density, specific gravity, degrees API, viscosity, Batching and special equation type one.

5. Configure the live outputs. Analog Outputs Turn to page 11.73 Pulse Outputs Turn to page 11.78

6. Multi-view display

7. Alarms and Events All reference information is in Chapter 8.

8. Serial communications ports All reference information is in Chapter 7.

9. Set-up 7951 Flow Computer securitySet passwords for security levels, and set-up the optional security fallback feature. (If not using the security key, change to the Engineer security level for the remainder of the configuration work).


7951 2510 (Ch11/DD) Page 11.5

11.4 Reference Page Conventions Most reference pages consist of:

A short bullet-point list of measurements that can be set-up.

A drawing of the process showing key blocks, and how data interacts.

Menu navigation references.

A list of software parameters (menu-based data) associated with the process drawing.

Other reference pages consist of a brief explanation but no diagram. Menu references and a list of parameter are always present.

Menu reference notationA notation has been used as a much shorter method of explaining how to navigate from the present menu to another menu. As an example, the notation of <“Configure”>/<“Flow rate”> translates into these steps:


Step 2: Use the DOWN-ARROW button to scroll through pages until the word “Configure” is seen.




Sometimes, it is convenient to use the MAIN-MENU button (especially if lost). However, use of the BACK-ARROW button is a much more common method of returning to a menu level.

Note: Menus may vary to other software versions and releases.


Page 11.6 7951 2510 (Ch11/DD)

11.5 Analog Inputs

Features: (Note: Example connections are located in Chapter 2.)

Analog Inputs supported by a 7951 (D-Type) with extra I/O option RTD/PT100 input channels (Analogue inputs 1 to 4) mA input channels (Analog inputs 1 to 10)

Analog Inputs supported by a 7951 (Klippon) with extra I/O option RTD/PT100 input channels (Analog inputs 1 to 4) mA input channels (Analog inputs 1 to 8)

What to do:

This reference page will assist when configuring basic data for all analog channels that are being used.

After each analog channel is set-up, check that a “Live” reading - a percentage by default - is being displayed by the corresponding <Input Channel> parameter. A “Fail” status indicates an absent or failed transmitter.

Later reference pages will expect all instrumentation to be already wired to the 7951 and expect there to be a live reading. Configuring a measurement task will then involve setting range (scaling) information and selecting the appropriate analogue channel as the source.

Menu Navigation List:

(1) <“Configure”>/<“Inputs”>/<”Analog inputs”> and (2) <“Health check”>/<“Inputs”>/<”Analog inputs”>

Parameter List: * shows data that can be “Live” or “Set”

Analogue Channel (and signal types) Parameters Analogue Channel

(and signal types) Parameters

Input channel 1 * Input channel 6 * Analog input1 type Analog input6 type Analogue Input 1 1

(RTD/PT100 or mA) mA input 1 ave type

Analogue Input 6 (mA only)

mA input 6 ave type Input channel 2 * Input channel 7 *

Analog input2 type Analog input7 type Analogue Input 2 1(RTD/PT100 or mA)

mA input 2 ave type




mA input 3 ave type




mA input 4 ave type



Analog input5 type Analog input10 type Analogue Input 5 (mA only)

mA input 5 ave type


mA input 10 ave type Abbreviation used: "ave" = average

1 There is a DIP-switch block on the processor board for deciding if this is a mA-type input or a RTD/PT100-type input.


7951 2510 (Ch11/DD) Page 11.7

11.6 Digital Inputs

Features: (Note: Rear panel pin connection information is located in Chapter 2)

Digital Inputs supported by a 7951 (D-Type) Status input channels 1 to 8 (without extra I/O option), or Status input channels 1 to 16 (with extra I/O option)

Digital Inputs supported by a 7951 (Klippon) Status input channels 1 to 6

What to do:

This reference page will assist when configuring parameters for all the Status Input channels that are being used.

None of the digital inputs have a default function. However, they can be allocated a function when setting up proving functions, and when requiring any of the following features:

Remote Print Transmit a current report through a serial port that is configured for connection to a printer. Selection of the input is made using parameter: <”Remote print Din”>

Maintenance-mode Attempt a switch to “maintenance-mode” from the “normal” mode. Selection of the input is made using parameter: <”Maint mode req Din”>. (To succeed in changing mode, this function requires the Flow Computer to be in a “Flow Stop” state).

Within the <“Health Check”> menu, there is a Status Input sub-menu. It contains a parameter with a series of digits on the second display line. Each digit indicates the present state of an individual input.


(1) <“Configure”>/<“Inputs”>/<”Status inputs”>, (2) <“Configure”>/<“IO physical alloc”> and (3) <”Health check”>/<"Inputs">/<”Status inputs”>


Digital In Channel

Parameters Digital In Channel

Parameters Digital In Channel

Parameters

DIN 1 logic level DIN 7 logic level DIN13 logic level 1DIN 1 mode level

7DIN 7 mode level

13DIN13 mode level

DIN 2 logic level DIN 8 logic level DIN14 logic level 2

DIN 2 mode level 8

DIN 8 mode level 14

DIN14 mode level DIN 3 logic level DIN 9 logic level DIN15 logic level

3DIN 3 mode level

9DIN 9 mode level

15DIN15 mode level

DIN 4 logic level DIN10 logic level DIN16 logic level 4

DIN 4 mode level 10

DIN10 mode level 16

DIN16 mode level DIN 5 logic level DIN11 logic level

5DIN 5 mode level

11DIN11 mode level

DIN 6 logic level DIN12 logic level 6

DIN 6 mode level 12

DIN12 mode level Abbreviation used: "DIN" = Digital Input


Page 11.8 7951 2510 (Ch11/DD)

11.7 Pulse Inputs

Features: (Note: Rear panel pin connection information is located in Chapter 2)

7951 (Klippon): Pulse Input 1 – for use by a pulse-based volumetric flowmeter

7951 (D-Type): Pulse Input 1 – for use by a pulse-based volumetric flowmeter Pulse Input 2 – for use by Master Meter Proving feature

What to do:

Use this reference page to configure the basic live input data for any of the channels. The reference pages for configuring further flow metering details will expect the instrumentation to be already wired to the 7951, and expect the “Live” pulse frequency. Master Meter Proving is described in Chapter 16B.

After each channel is set-up, check on the pulse frequency that is being indicated by the <”Flow meter frequency”> parameter. Use the Health Check menu to view other diagnostic information such as a missing pulse counter.


(1) <“Configure”>/<“Inputs”>/<“Pulsed flow inputs”> (2) <“Configure”>/<“Flow meter”>/<”Turbine/PD details”> (3) <“Health check”>/<“Inputs”>/<“Pulse inputs”>


Pulse Channel (and allocation) Parameters Notes? Pulse Channel

(and allocation) Parameters Notes?

Flow meter frequency * B Prover turb freq * BPIN 1 input type PIN 2 input type PIN 1 error limit A PIN 2 error limit A

Pulse input 1 value Pulse input 2 value Err Pulse ip 1 value C Err Pulse ip 2 value C

Pulse Input 1 (Flowmeter)

PIN 1 sample time

Pulse Input 2 (Master Meter)

PIN 2 sample time Abbreviation used: "PIN" = Pulse Input

Notes:

A The programmed error limit for missed pulses is not applicable unless there are dual pickup pulse trains being received by the Flow Computer.

B The pulse frequency is calculated using the following equation:

Using: tPF

Where: F is the pulse frequency

P is the number of pulses accumulated over elapsed time ‘t’ {Health Check parameter is <Err Pulse ip N value> where ‘N’ identifies the pulse input}

t is the elapsed time (in seconds) since the previous pulse count was used in this calculation. {Health Check parameter is <Pulse ip N sample> where ‘N’ identifies the pulse input}

Each live pulse input is read every 100ms. Accumulated pulses are then displayed every machine cycle.

C Counter for missing (error) pulses during the present machine cycle. There is also a totaliser for accumulating the number of missing pulses from each cycle.


7951 2510 (Ch11/DD) Page 11.9

11.8 Turbine/PD Flow

Measurements and Features Supported: Indicated Volume and Gross Volume flow rate at the metering point. 4 x Flowmeter calibration curve options.

Figure 11.1: Turbine/PD Flow Blocks and Parameters

Menu Navigation List: (1) <“Configure”>/<”Inputs”><Flow meter”><“Turbine/PD details”>/<”Main turbine/PD”> (2) <“Configure”>/<“Flow rate”> and (3) <“Health check”>/<“Inputs”>/<”Flowmeter inputs”>/<”Turbine”>


Index Parameters Notes? Index Parameters Notes? 1 Flow meter frequency * A 56 Curve4 K at Q1 2 Turb freq HI lmt : : : :3 Flow stop threshold 65 Curve4 K at Q10 4 Meter curve type B 66 Frequency Q1 5 Meter curve points : : :6 Error% / Kfactor 1 75 Frequency Q10 : : : : 76 Curve 1 visc LO lmt

15 Error% / Kfactor 10 77 Curve 2 visc LO lmt 16 Flow/freq 1 78 Curve 3 visc LO lmt : : : 79 Curve 4 visc LO lmt

25 Flow/freq 10 80 Curve 4 visc HI lmt 26 Curve1 K at Q1 81 Hysteresis : : : : n Meter kinematic visc * 35 Curve1 K at Q10 82 Turb curve selected 36 Curve2 K at Q1 83 Polynomial degree : : : : 84 Polynomial coeff a0 45 Curve2 K at Q10 : : : : 46 Curve3 K at Q1 95 Polynomial coeff a10 : : : : 96 Flowmeter K factor * (B)

55 Curve3 K at Q10 97 Indicated vol rate *


Page 11.10 7951 2510 (Ch11/DD)

TURBINE/PD FLOW CONFIGURATION

(Parameter list continued…) * shows data that can be “Live” or “Set”

Index Parameters Notes? Index Parameters Notes? 98 Meter factor * (B) 101 Gross vol LO lmt D 99 Gross volume rate * 102 Rate flowstop action C 100 Gross vol HI lmt D - Flow meter

Notes: (X) – Indirectly mentioned in note A Refer to Section 11.7 on page 11.8 for details of configuring this parameter.

B There are four turbine calibration options supported: (1) “Turbine correction” (Default)

A ‘K-factor’ is linearised, once every machine cycle, from a user-programmable calibration curve. The ‘Meter factor’ (MF) is a single SET value. They may then be updated by a proving session, by product detection or by a MODBUS networked device. Also, see Figure 11.2 on page 11.10.

(2) “Turbine conversion”The ‘Meter Factor’ (MF) is calculated, once every machine cycle, by a relative error (percentage) correction process. The ‘K-factor’ is a single SET value. They may then be updated by a provingsession, by product detection or by a MODBUS networked device. Also, see page 11.11.

(3) “4 x (K v Freq)” (Viscosity Corrected Flow) A ‘K-factor’ is interpolated, once every machine cycle, from one of four programmable calibration curves. Curve selection is determined by the present viscosity range. The ‘Meter factor’ (MF) is a SET value. Also, see Figure 11.3 on page 11.11

(4) “UCC polynomial” (Viscosity Corrected Flow) The ‘K-factor’ is a single SET value. A ‘Meter Factor” (MF) is calculated, once every machine cycle, using the polynomial equation from Section 3.3.3.2 of the ISO 4124:1994(E) International Standard. Parameters to be programmed into the Flow Computer are the pre-generated factors (a0, a1, etc.) for an established curve fit and the polynomial degree. (Viscosity measurements must also be set-up). This method is for when using some turbines, such as helecoidal two-blade turbine meters, to meter multi-product oils or meter products where large viscosity variations can occur. Full details of the method are provided in the ISO 4124:1994(E) International Standard.

Proving sessions can overwrite either a ‘Meter Factor’ value or the ‘K-factor’ value. It is dependent on how proving is configured and if the prove session is successful.

Product detection can also overwrite a ‘Meter Factor’ (MF) value and/or the ‘K-factor’ value – see page 11.74.

C By default, the Flow Computer calculates and displays live flow rates under a ‘Flow stop’ condition, even when there is negligible flow. However, displayed rates can be forced to zero by selecting the option descriptor with “Zero flow rates”. (Calculations using a flow rate value as an input will always get zero values during ‘Flow stop’)

D Keep both ‘HI’ and ‘LO’ limits programmed (SET) with a zero value if an alarm limit check is not required.

Figure 11.2: ‘K Factor’ v Pulse Frequency Calibration Curve

Figure 11.2 shows an example of a calibration curve profile with 4 points programmed.

The lowest frequency on curve is point (F1, Kf1). This point corresponds to the <“Flow/freq 1”> parameter value, and the <“Error% / Kfactor 1“> parameter value respectively.

Highest frequency on curve is point (F4, Kf4). This point corresponds to <“Flow/freq 4”>, <“Error% / Kfactor 4“>.

Point (FM, Kfm) corresponds to a live pulse frequency and a resulting ‘K Factor’.

'K' Factor(Pulse/m3)

Kf1Kf3

Kf2

Kf4

F1 F2 F3 F4

PulseFrequency

Kfm

Fm


7951 2510 (Ch11/DD) Page 11.11

CONFIGURATION TURBINE/PD FLOW

Figure 11.3: 4 x ‘K- factor’ v Pulse Frequency Calibration Curves (Viscosity Corrected Flow)

Quad curve profiles: A curve is selected by checking the metering-run kinematic viscosity value against range limits for each curve.

Lowest frequency on curve 1 is point (F1, Kf1). This corresponds to <“Frequency Q1”> parameter, and <“Curve 1 K at Q1”> parameter, respectively.

Highest frequency on curve 1 is point (F5, Kf5). This corresponds to <“Frequency Q5”> parameter, and <“Curve 1 K at Q5”> parameter, respectively.

Point (FM, Kfm) corresponds to a live pulse frequency and a resulting ‘K Factor’ from the selected curve.

For the purpose of this example, C3 is the selected curve with the Meter Kinematic Viscosity value falling in the appropriate range for that curve. The Flow Computer re-checks the range every machine cycle. Hysteresis can be used with the viscosity ranges to avoid frequent switching between two curves.

‘Meter Factor’ from Flow versus Error Percentage Calibration Curve Turbines are supplied with a calibration certificate that describes the actual flow rates against percentage error in readings by a test meter.

Table 11.2: Example of Certificate Data

Flow rate (m3/h) 400 280 160 100 Error % 0.11 0.17 0.06 -0.24

The raw data on the certificate has to be turned into turbine corrected values by the Flow Computer. To do this, a single curve profile must be set-up in the following way:

Parameters Value or Option Meter curve type “Turbine conversion” Please note that this is an example and that only data

Meter curve points “4 curve points” from the calibration certificate of the turbine should Flow/freq 1 100 be entered into the Flow Computer. Flow/freq 2 160 Flow/freq 3 280 Flow/freq 4 400

Error% / Kfactor 1 -0.24 Error% / Kfactor 2 0.06 Error% / Kfactor 3 0.17 Error% / Kfactor 4 0.11

Turbine corrected values are not displayed within the menu system but the calculations used are as follows:

Where:

tV = Corrected volume from test turbine

aV = Actual volume (e.g. 100 from the above data)

tE = Corrected percentage error in test turbine reading

aE = Actual error in Vt reading (e.g. -0.24 from the above data)

a

att V

VVE

100**a

aat V

EVV

100*


Page 11.12 7951 2510 (Ch11/DD)

TURBINE/PD FLOW CONFIGURATION

The calculations use the SET curve profile data to get a modified curve.

Table 11.3: Example Modified Curve with Turbine Corrected Values

Flow rate (m3/h) 400.44 280.476 160.096 99.76 Error % 0.1098 0.1697 0.05996 -0.241

With a ‘Live’ (or SET) indicated volume flow rate an error percentage can be linearised from the modified curve. The error percentage is then used to adjust the present ‘Meter Factor’ value.


7951 2510 (Ch11/DD) Page 11.13

CONFIGURATION ADDITIONAL FLOW RATES

Measurements and Features Supported:Indicated standard volume flow rate at the metering point Gross standard volume flow rate at the metering point Mass flow rate at the metering point

Figure 11.4: Additional Turbine Flow Rates Blocks and Parameters

Menu Navigation List: (1) <“Configure”>/<“Flow rate”>, (2) <“Flow rates”>, (3) <“Density”> and (4) <“Configure”>/<“Base density”>


Index Parameters Notes? Index Parameters Notes?

97 Indicated vol rate * 110 Ind std vol rate * 98 Meter factor * 111 Ind std vol HI lmt B 99 Gross volume rate * 112 Ind std vol LO lmt B 102 Rate flowstop action A 113 Gross std vol rate * 103 CTL 114 Gross std vol HI lmt B 104 CPL 115 Gross std vol LO lmt B 105 Meter density * 116 Mass rate * 106 Base density value * 117 Mass rate HI limit B 107 Dens calc sel 118 Mass rate LO limit B 108 VCF * 109 CCF *

Notes: A By default, the Flow Computer calculates and displays actual live flow rates under a ‘Flow stop’ condition, even

when there is negligible flow. However, displayed rates can be forced to zero by selecting the option descriptor with “Zero flow rates”. (Calculations using a flow rate value as an input will always get zero values during ‘Flow stop’)

B Keep both ‘HI’ and ‘LO’ limits programmed (SET) with a zero value if an alarm limit check on the associated rate is not required.


Page 11.14 7951 2510 (Ch11/DD)

TURBINE/PD FLOW METERING EQUATION LIST

Equation List:

Equation TU#1: Indicated Volume flow rate

Using: QIV = 3600*Kff

Where: QIV = Indicated Volume flow rate (m3/hour)….….…… {Parameter: <”Indicated vol rate”>}

f = Flowmeter (pulse) frequency (pulse/sec)…...…. {Parameter: <”Flow meter frequency”>}

Kf = ‘K factor’ (pulses per m3)…………..…………….. {Parameter: <”Flowmeter K factor”>}

Equation TU#2: Gross Volume flow rate

Using: QGV = MF*QIV

Where: QGV = Gross Volume flow rate (m3/hour)………....…… {Parameter: <”Gross volume rate”>}

QIV = Indicated Volume flow rate (m3/hour)….….…… {See Equation TU#1}

MF = Meter Factor………………………………………. {Parameter: <”Meter factor”>}

Equation TU#3: Volume Correction Factor

Using: VCF = CPL*CTL ........………….…………….………..... (API)

Or: VCF =B

...................…….………………………...... (4x5)

Where: VCF = Volume correction factor…………………...……. {Parameter: <”VCF”>} CTL = API temperature correction factor…….…..……. {Parameter: <”CTL”>}

CPL = API pressure correction factor……..……………. {Parameter: <”CPL”>}

And: = Fluid density at a metering-point…….…….....… {Parameter: <”Meter density”>}

B = Fluid density at base conditions….….…….....… {Parameter: <”Base density value”>}

(Note: The equation choice is linked to the selected method for density referral)

Equation TU#4: Combined Correction Factor

Using: CCF = MF*CPL*CTL …………………...…………....... (API)

Or: CCF = MF*B

.......………………………………....... (4x5)

Where: VCF = Volume correction factor…………………...……. {Parameter: <”CCF”>} CTL = API temperature correction factor…….…..……. {Parameter: <”CTL”>}

CPL = API pressure correction factor……..……………. {Parameter: <”CPL”>}

MF = Meter Factor………………………………………. {Parameter: <”Meter factor”>}

And: = Fluid density at a metering-point…….…….....… {Parameter: <”Meter density”>}

B = Fluid density at base conditions….….…….....… {Parameter: <”Base density value”>}

(Note: The equation choice is linked to the selected method for density referral)


7951 2510 (Ch11/DD) Page 11.15

EQUATION LIST TURBINE/PD FLOW METERING

(Equation List continued…)

Equation TU#5: Indicated Standard Volume flow rate

Using: QISV = QIV * VCF

Where: QISV = Indicated Standard Volume flow rate…...……… {Parameter: <”Ind std vol rate”>}


VCF = Volume correction factor…………………...……. {See Equation TU#3}

Equation TU#6: Gross Standard Volume flow rate

Using: QGSV = QIV * CCF

Where: QGSV = Gross Standard Volume flow rate……….……… {Parameter: <”Gross std vol rate”>}


CCF = Combined correction factor…………………..…. {See Equation TU#4}

Equation TU#7: Mass flow rate

Using: QM = QGV *

Where: QM = Mass flow rate (kg/hour)……………...………….. {Parameter: <”Mass rate”>}

QGV = Gross Volume flow rate (m3/hour)………....…… {See Equation TU#2}

= Fluid density at a metering-point…….…….....… {Parameter: <”Meter density”>}


Page 11.16 7951 2510 (Ch11/DD)

11.9 ORIFICE FLOW METERING (ISO 5167-1 2)Measurements and Features Supported: Prime Selected Differential Pressure – across the Flowmeter.

Mass Rate at the metering point - from ISO 5167-1 (this page), HART Input (Page 11.18) or AGA 3 (Page 11.17). Gross Volume flow rate at the metering point – turn to page 11.18.

Menu Navigation List:(1) <“Configure”>/<”Inputs”>/<“Flow meter”>, (2) <“Health check”>/<”Inputs”>/<“Flow meter inputs”>/<“Orifice”>, (4) <“Configure”>/<“Flow rate”>, (5) <“Density”>/<”Meter run density”>, (6) <“Pressure”>/<”Meter run pressure”>, (7) <”Temperature”>/<“Meter run temperature”> and (8) <“Health check”>/<”Flow meter details”>/<”Orifice”>

Parameter List: * shows data that can be “Live” or “Set” Index Parameters Notes? Index Parameters Notes?

- Flow meter 26 Orif pipe diameter 1 DP cell 1 input src A 27 Orifice diameter 2 DP cell 2 input src A 28 Header dynamic visc * L 3 DP cell 3 input src A 29 Orifice isentropic 4 DP cell 4 input src A 30 Pipe expans coeff 5 DP cell 5 input src A 31 Orif expans coeff 6 Diff press HI 100% 32 Orifice cal temp 7 Diff press HI 0% 33 Orif tapping code 8 Diff press MED 100% 34 Venturi type 9 Diff press MED 0% 35 Orif discharge coeff J

10 Diff press LO 100% 36 Orif expandability J 11 Diff press LO 0% 37 Orif vel of approach J 12 Diff press config B 38 Reynolds number 13 Diff press HI switch C 39 Orif corr pipe dia 14 Diff press LO switch C 40 Corr orif diameter 15 Diff press cal error D 41 Orifice beta 16 Diff press cal time D 42 Pressure loss 17 DP deviation limit E 43 Pressure ratio 18 DP input alarms F 44 Mass rate K factor 19 Diff press range G 45 Meter density * 20 Diff press HI lmt 46 Mass rate * H 21 DP flow stop limit 47 Orif mass flow calc 22 Diff press FB type t Meter temperature * 23 Diff press FB value P Meter pressure * 24 Diff press value * Menu(2) - Rate flowstop action I 25 Orifice type - Flow status I

Notes are on page 11.19. 2 Standards used: ISO 5167-1:1991 and ISO 5167-1:1991/Amd.1:1998(E). Refer to the Standard for details of restrictions.


7951 2510 (Ch11/DD) Page 11.17

ORIFICE FLOW METERING (AGA 3 3)

Measurements and Features Supported: Prime Selected Differential Pressure across the flowmeter

Mass Rate at the metering point - from AGA 3 or from ISO 5167 (Page 11.16) or from a HART Input (Page 11.18) Gross Volume flow rate at the metering point - See Page 11.18

Figure 11.5: Orifice Flow (AGA 3) Blocks and Parameters

Menu Navigation List:(1) <“Configure”>/<”Inputs”>/<“Flow meter”>, (2) <“Health check”>/<”Inputs”>/<“Flow meter inputs”>/<“Orifice”> (4) <“Configure”>/<“Flow rate”>, (5) <“Density”>/<”Meter run density”>, (6) <“Pressure”>/<”Meter pressure”> (7) <”Temperature”>/<“Meter run temperature”> and (8) <“Health check”>/<”Flow meter details”>/<”Orifice/PD”>



- Flow meter 25 Orif pipe diameter 1 DP cell 1 input src A 26 Orifice diameter 2 DP cell 2 input src A 27 Header dynamic visc * L3 DP cell 3 input src A 28 Orifice isentropic 4 DP cell 4 input src A 29 Pipe expans coeff 5 DP cell 5 input src A 30 Orif expans coeff 6 Diff press HI 100% 31 Orifice cal temp 7 Diff press HI 0% 32 Orif tapping code 8 Diff press MED 100% 33 Orif discharge coeff J 9 Diff press MED 0% 34 Orif expandability K

10 Diff press LO 100% 35 Orif vel of approach J 11 Diff press LO 0% 36 Reynolds number 12 Diff press config B 37 Orif corr pipe dia 13 Diff press HI switch C 38 Corr orif diameter 14 Diff press LO switch C 39 Orifice beta 15 Diff press cal error D 40 Orif mass K factor 16 Diff press cal time D 41 Meter density *17 DP deviation limit E 42 Mass rate * H18 DP input alarms F 43 Orif mass flow calc 19 Diff press range G t Meter temperature *20 Diff press HI lmt P Meter pressure *21 DP flow stop limit - Rate flowstop actions I 22 Diff press FB type - Flow status I 23 Diff press FB value 24 Diff press value * Menu(2)

Notes are on page 11.19.

3 Standard used: AGA report 3 (November 1992, Third edition). Refer to the Standard for details of restrictions.


Page 11.18 7951 2510 (Ch11/DD)

ORIFICE FLOW METERING (HART)

Measurements Supported:Mass Rate at the metering point - from a HART Input or from ISO 5167 (Page 11.16) or from AGA 3 (Page 11.17) Gross Volume flow rate at the metering point

Figure 11.6: Orifice Flow (HART) Blocks and Parameters

Menu Navigation List: (1) <“Configure”>/<“Flow rate”> (2) <“Configure”>/<”Inputs”>/<“Flow meter”> (3) <”Base density/SG”>/<”Base density”>



- Flow meter 7 Mass rate *1 Mass rate HART chl 8 Rate flowstop action I2 Orif mass flow calc 9 Gross volume rate * **3 Mass rate HI limit Base Base density value *4 Mass rate LO limit - Flow status I5 Mass rate FB type 6 Mass rate FB value

Notes are on page 11.19. ** See “Extra Information” Section

Extra Information:

Calculation: Gross Volume flow rate

Use: GVQ =Meter

mQ

Where: GVQ = Gross Volume flow rate..……….. {Parameter: <”Gross volume rate”>}

mQ = Mass flow rate……………………. {Parameter: <”Mass rate”>}

Meter = Metering density…………………. {Parameter: <”Meter density”>}


7951 2510 (Ch11/DD) Page 11.19

ORIFICE FLOW METERING (ISO 5167-1/AGA3/HART)

Notes: (for “Orifice Flow Metering” pages) A By default, every P measurement channel is configured to use the transmitter wired to Analogue Input ‘1’. Re-

configure P measurement channels to use other live inputs by editing the source selection parameter. A cell can be connected to any available analogue input or even attached to a HART network loop. If using HART, any unique HART (protocol) address can be given to a cell. (Refer to Chapter 17 for HART coverage) Do not be concerned about the effect of an unused cell input without a “None” option descriptor selected. A selected configuration - cell arrangement - code informs the 7951 of the cell inputs to read and processed.

B Table 11.4 shows a selection of configuration codes (option descriptors) for the more likely ‘pay’ and ‘check’ cell arrangements. Other combinations involving 5 cells can be selected.

Table 11.4: Selection Codes, Cell Arrangements and Pressure Range Switching

Configuration Code Cell Arrangement Range Selection?

H=DP:1 ‘Pay’ Cell #1 - always the primary - covers a high pressure range. No

H=DP:12 ‘Pay’ Cell #1 and ‘Check’ Cell #2 cover exactly the same high range. No

H=DP:1 L=DP:2 ‘Pay’ Cell #1 covers the high range. ‘Pay’ Cell #2 covers the low range. Yes

H=DP:12 L=DP:3 Cell #1 (‘Pay’) and Cell #2 (‘Check’) cover exactly the same high range. Cell #3 (‘Pay’) covers the low pressure range. Yes

H=DP1 M=DP2 L=DP3

Cell #1 (‘Pay’) used for high pressure range. Cell #2 (‘Pay’) used for medium range. Cell #3 (‘Pay’) used for low pressure range. Yes

H=DP:12 L=DP:34 Cells #1 (‘Pay’) and #2 (‘Check’) cover the high pressure range. Cells #3 (‘Pay’) and #4 (‘Check’) cover the low pressure range. Yes

H=DP:1p23 L=DP:4p5

Cells #1 (‘Pay’), #2 (‘Check’) and #3 (‘Check’) cover the high range. Cells #4 (‘Pay’) and #5 (‘Check’) cover the low pressure range. Yes

C ‘LO switch’ is a low point marker in terms of a percentage 4 of the presently selected pressure range. A 7951 calculated DP value, resulting from this programmed (SET) percentage, is the boundary at which primary use of a ‘pay’ DP Cell is automatically switched to another ‘pay’ DP Cell with a lower range. This switch will provide measurements that are more accurate.

‘HI Switch’ is a high point marker in terms of a percentage of the presently selected pressure range. A 7951 calculated DP value, resulting from this programmed (SET) percentage, is the boundary at which primary use of a ‘pay’ DP Cell is automatically switched to another ‘pay’ DP Cell with a higher range. This switch will provide measurements that are more accurate.

D Optional feature: ‘Calibration error’ (i.e. limit) Checks. <“Diff press cal error“> is the alarm limit for the maximum difference in differential pressure measurements between a selected (prime) DP Cell and the next suitable (prime) DP Cell. An alarm is raised if the limit is exceeded for longer than a period as SET by <“Diff press cal time”>. (Not enabled when limit is SET to 0).

E Deviation refers to difference in differential pressure measurements between ‘Master’ (or ‘Pay’) DP Cell and any ‘Check’ DP Cells.

F Automatic selection of a ‘higher’ range DP Cell can cause a mA input failure alarm to be raised even though the transmitter has not actually failed. The cause of this alarm is the mA signal from a ‘lower’ range cell exceeding 111% of the 20mA analogue input range as the cell continues to measure beyond it’s effective range. This alarm condition remains until the lower range cell is re-selected. <“DP inputs alarm”> gives the option of suppressing the alarm under this particular situation. By default, there is no suppression.

4 Alternative units, such as particles per million, may be shown on-screen.


Page 11.20 7951 2510 (Ch11/DD)

ORIFICE FLOW METERING (ISO 5167-1/AGA3/HART)

Notes continued… G Identifies the range - low, medium or high - of the selected primary ‘pay’ DP Cell. (Read-only data value).

H The “Reynolds Number” calculation is iterative and requires a previous value for the mass flow rate. This is the reason for showing the mass rate by an Orifice calculation block.

I The <“Flow status”> parameter is located within the INFORMATION button menu. It shows if the Flow Computer considers there to be either normal flow or zero flow in the meter-run pipe. Flow stop (zero flow) thresholds, such as <“DP flow stop limit”>, are used to force live flow rates to 0 and

therefore halt flow totals even when there is negligible flow. <“Flow status”> will show “Flow stopped”. However, negligible flow rate values may still be displayed if enabled by the <“Rate flowstop actions”> parameter.

In the case of an Orifice System, the DP value must be greater than the setting of <“DP flow stop limit”> for normal flow. <“Flow status”> will then show “Flowing”.

J Support for the use of other primary DP devices is made possible with the ability to programme (SET) values for the Velocity of approach and the Discharge coefficient. For this software feature, these values can be programmed (SET) to a known value only by using the “Flow Meter” Wizard.

K The liquid expansibility factor has a fixed value of 1.

L See “Prime Viscosity” reference pages, starting on page 11.52.


7951 2510 (Ch11/DD) Page 11.21

ORIFICE PLATE/VENTURI EQUATIONS

Equation List: The equations that follow are common to both ISO 5167-1:1991, ISO 5167-1:1991/Amd:1998 and AGA 3 standards unless otherwise stated. Refer to the appropriate Standard for information on any restrictions not listed here.

Support for the use of other primary DP devices is made possible with the ability to ‘Set’ values for the Velocity of approach and the Discharge coefficient. For this software feature, these values can be programmed (SET) to a known value only by using the “Flow Meter” Wizard.

Equation OR#1: Mass flow rate The mass flow rate is related to differential pressure by the following equation:

Using: mQ = 3600**1000

P*K

Where: mQ = Mass flow rate (in Kg/hour)...……….............................. {Parameter: <“Mass rate”>}

K = Mass flow rate ‘K’ factor............…..……….................... {See Equation OR#2}

P = Differential pressure measurement (in mbar)…….….... {Parameter: <“Diff press value”>}

= Density of measured fluid.........................……….......... {Parameter: <“Meter density”>}

Equation OR#2: Mass flow rate ‘K’ factor

Using: K = 12 N*d**E*C

Where: K = Mass flow rate ‘K’ factor.................……….................... {Parameter: <“Orif mass k factor”>}

C = Discharge coefficient..........................………................ {See equations OR#9a to OR#9d}E = Velocity of approach factor.......................…….…......... {See Equation OR#5}

= Liquid expansibility factor = 1...................……….......... {Parameter: <”Orif expandability”>}

'd = Orifice diameter, corrected for expansion.....………..... {See Equation OR#3a}

1N = 1000*10*42* 5 = 0.0003512407367 ……….. {Actual constant used}

= 3.141592654.........................................………............. {Actual constant used}

Equation OR#3: Correction for area expansion of the orifice and pipe

Using: 'd = 6oc 10*E*tt1*d …………….……………..…. OR#3a

Where: 'd = Orifice diameter, corrected for expansion……….......... {Parameter: <“Orif corr pipe dia”>}

d = Orifice diameter at calibration temperature ‘tc’……….... {Parameter: <“Corr orif diameter”} t = Temperature at the metering-run..................………..... {Parameter: <“Meter temperature”>}

ct = Orifice calibration temperature....................………....... {Parameter: <“Orifice cal temp”>}

oE = Orifice expansion coefficient.......................………....... {Parameter: <“Orif expans coeff”>}

Using: D' = 6Pc 10*E*tt1*D ………………………..…….. OR#3b

Where: D' = Pipe diameter, corrected for expansion........……..….... {Parameter: <“Orif corr pipe dia”>}

D = Pipe diameter at calibration temperature ‘toc’..….…..... {Parameter: <“Orifice diameter”>}

t = Temperature at the metering-run.................……..…..... {Parameter: <“Meter temperature”>}

ct = Orifice plate calibration temperature...........………........ {Parameter: <“Orifice cal temp”>}

PE = Pipe expansion coefficient.........………......................... {Parameter: <“Pipe expans coeff”>}


Page 11.22 7951 2510 (Ch11/DD)



Equation OR#4: Diameter ratio

Uses: = 'D'd

Where: = Beta ratio (no units)…………………….………………. {Parameter: <“Orifice beta”>}

'd = Orifice diameter, corrected for expansion………........ {Parameter: <“Corr orif diameter”>}

D' = Pipe diameter, corrected for expansion......…….….... {Parameter: <“Orif corr pipe dia”>}

Equation OR#5: Velocity of approach factor

Using: E = 21

41

Where: E = Velocity of approach factor..............…………............. {Parameter: <“Orif vel of approach”>}

= Diameter ratio........................................…………....... {See Equation OR#4}

Equation OR#6a: (ISO 5167) Reynolds number for discharge coefficient

Using: edR = '*D*

10*4*3600Q 6

m

Where: edR = Reynolds number............………….......................... {Parameter: <“Reynolds number”>}

mQ = Mass flow rate from previous cycle….…................. {See Equation OR#1} = 3.141592654...................................………….......... {Actual constant used}

D' = Pipe diameter (corrected for expansion)………....... {See Equation OR#3b}

= Dynamic viscosity................………......................... {Parameter: <“Meter dynamic visc”>}

Equation OR#6b: (AGA3) Reynolds number for discharge coefficient

Using: edR ='*D10*4*

3600Q*N

6m

2

Where: edR = Reynolds number....................………...................... {Parameter: <“Reynolds number”>}

2N = 1273239.5.....................................………................ {Actual constant used}

mQ = Mass flow rate from previous cycle…...................... {See Equation OR#1}

'D = Pipe diameter (corrected for expansion)………....... {See Equation OR#3b} = Dynamic viscosity...................................………...... {Parameter: <“Meter dynamic visc”>}

Equation OR#7a: STOLZ (ISO 5167-1:1991) Discharge coefficient for Orifice Plate

Basic Equation Component

Use: 1C =75.0

ed

65.281.2

R10**0029.0*184.0*312.05959.0

Where: 1C = Basic equation component

= Diameter ratio......................…………......................... {See Equation OR#4}

edR = Reynolds number.............................………................ {See Equation OR#6a}


7951 2510 (Ch11/DD) Page 11.23



For Corner Tappings only

Use: C = 1C

Where: C = Discharge coefficient...................……….................... {Parameter: <“Orif discharge coeff”>}

1C = The basic equation component........………............... {See above}

For D and D/2 tappings only

Use: C = 31441 *015839.01**039.0C

Where: C = Discharge coefficient...........………......................... {Parameter: <“Orif discharge coeff”>}

1C = Basic equation component...........………................ {See above}

= Diameter ratio...................………............................ {See Equation OR#4}

For Flange Tappings where the pipe diameter (corrected for expansion) is larger than 58.62mm

Use: C = 31441 *

'D85598.01**039.0C

Where: C = Discharge coefficient..................……….................. {Parameter: <“Orif discharge coeff”>}

1C = Basic equation component.............………............... {See above}

= Diameter ratio..............................………................. {See Equation OR#4}D' = Pipe diameter (corrected for expansion)..…..……... {See Equation OR#3b}

For Flange Tappings where the pipe diameter (corrected for expansion) is less than or equal to 58.62mm

Use: C = 31441 *

'D85598.01**

'D286.2C

Where: C = Discharge coefficient.....……….................................. {Parameter: <“Orif discharge coeff”>}

1C = Basic equation component.......………....................... {See above}

= Diameter ratio.................................……....…….......... {See Equation OR#4}

D' = Pipe diameter (corrected for expansion)……..…....... {See Equation OR#3b}

Equation OR#7b: (ISO 5167-1:1991) Discharge coefficient for a Venturi tube

C = 0.984 when there is an ‘as cast’ convergent section where: - 100mm D 800mm 0.3 0.75 2 * 105 Red 2 * 106

C = 0.995 when there is a machined convergent section where: - 50mm D 250mm 0.4 0.75 2 * 105 Red 1 * 106

C =0.985 when there is a rough welded sheet iron convergent section where:- 200mm D 1200mm 0.4 0.7 2 * 105 Red 1 * 106


Page 11.24 7951 2510 (Ch11/DD)


Equation OR#7c: (AGA3) Discharge coefficient for an Orifice Plate

Refer to part 4 of AGA report 3 (November 1992, Third edition) for details of the Reader-Harris/Gallagher equation.

Equation OR#7d: (ISO 5167-1:1998) Discharge coefficient for an Orifice Plate

Equation Terms and Parameter: C = Discharge coefficient……………………………………...………… {Parameter: <“Orif discharge coeff”>}

'D = Pipe diameter (corrected for expansion).....……………….……... {See Equation OR#3b}

= Diameter ratio....................……………………............................. {See Equation OR#4}

edR = Reynolds number..........................……………………................. {See Equation OR#7a}

Refer to section 8.3.2.1 of the ISO 5167-1:1991(E)/Amd.1:1998(E) Standard for details of the Reader-Harris/Gallagher equation.

Equation OR#8: Pressure ratio

Use: PR = 1

2PP

Where: PR = Pressure ratio...............................…………............... {Parameter: <“Pressure ratio”>}

1P = Pressure at up-stream tapping (in Bar)...…..……...... {No Parameter}

= 3Loss 10*PP

2P = Pressure at down-stream tapping (in Bar).……...…... {No Parameter} = PP1

And: P = Pressure measured at the metering-run……...…....... {Parameter: <“Meter pressure”>}

LossP = Pressure loss (in Bar)..........………..…...................... {Parameter: <“Pressure loss”>} = *25.13.1*P

Equation OR9: Gross Volume flow rate

Use: GVQ =Meter

mQ

Where: GVQ = Gross Volume flow rate..………………………………. {Parameter: <”Gross vol rate”>}

mQ = Mass flow rate…………………………..………………. {Parameter: <”Mass rate”>}

Meter = Metering density……………………………...…………. {Parameter: <”Meter density”>}


7951 2510 (Ch11/DD) Page 11.25

ORIFICE V-CONE EQUATIONS

Listed equations OVC#1 to OVC#5 are formulated from the standard flow equations as published by McCrometer, the V-Cone manufacturer. The remaining equations (OVC#6 to OVC#9) are provided for completeness and comply with the ISO 5167-1:1991 and ISO 5167-1:1991/Amd:1998 Standards.

Equation OVC#1: Mass flow rate The mass flow rate is related to differential pressure by the following equation:

Using: mQ = af4

22

c F*3600**C*P*1

*D**g*2*4

Where: mQ = Mass flow rate (in Kg/hour)............……......……........... {Parameter: <“Mass rate”>}

cg = Dimensional conversion constant = 1…….………...….. {Actual constant used}

= Density of measured fluid (in Kg/m3).........………..........{Parameter: <“Meter density”>}

D = Cone inner diameter (in metres), uncorrected…..…….. {Parameter: <“Pipe diameter”>}

= Meter beta (diameter) ratio (no units)……...………..… {See Equation OVC#4b}

P = Differential pressure measurement (in Pa)…….…….... {Parameter: <“Diff press value”>}

fC = Flow coefficient of the meter (no units)…………...……. {Parameter: <“Orif discharge coeff”>}

= Liquid expansibility factor = 1 (no units)…......……....... {Actual constant used}

aF = Meter thermal expansion factor…………………...…….. {See Equation OVC#2}

Note: The flow coefficient is not calculated when using a V-Cone meter. It is necessary to locate Cf on the calibration certificate and then ‘Set’ a value.

Equation OVC#2: Thermal expansion factor (Fa) If the material expansion coefficients of the pipe and the cone are the same…

Use: aF = 528t**21 PE ……………….……….……..……. OVC#2a

Where: aF = Meter thermal expansion factor………..…….………….. {No Parameter}

PE = Coefficient for thermal expansion per degree Rankine. {No Parameter}

t = Operating temperature (in degrees Rankine)….……… {Parameter: <”Meter temperature”>}

If the material expansion coefficients of the pipe and the cone are not the same…

Use: aF = 22

21

4

21

4

22

*D1*

'1

'*'D ……………..…………………….. OVC#2b

Where: aF = Meter thermal expansion factor………..………...……… {No Parameter}

D' = Cone inner diameter, corrected for expansion……..…. {See Equation OVC#4a}D = Cone inner diameter (in metres), uncorrected…..…….. {Parameter: <“Pipe diameter”>}

' = Beta ratio, corrected dimensions (no units)…….……… {See Equation OVC#3a} = Beta ratio, uncorrected dimensions (no units)…...….… {See Equation OVC#3b}

Equation OVC#3: Beta Ratio

Use: ' = 21

2

2

'D'd1 ………………….………..………………….. OVC#3a

Where: ' = Meter beta ratio (no units)………….….……….………... {Parameter: <“Orifice beta”>} d' = Cone outside diameter, corrected for expansion……. {See Equation OVC#4b}D' = Cone inner diameter, corrected for expansion……...…. {See Equation OVC#4a}


Page 11.26 7951 2510 (Ch11/DD)


(Equation OVC#3: Beta Ratio)

Use: = 21

2

2

Dd1 ………………………………..……....………OVC#3b

Where: = Meter beta ratio (no units)……….…………….……….... {No Parameter} d = Cone outside diameter, uncorrected for expansion…... {Parameter: <“Orifice diameter”>} D = Cone inner diameter, uncorrected for expansion……... {Parameter: <“Pipe diameter”>}

Equation OVC#4: Corrections for thermal expansion of V-Cone If the expansion coefficients of the pipe and the cone are not the same…

Use: D' = ctt**DD ……………………..………….…….. OVC#4a

Where: D' = Cone inner diameter, corrected for expansion……....… {Parameter: <“Orif corr pipe dia”>} D = Cone inner diameter (in metres), uncorrected……..….. {Parameter: <“Pipe diameter”>}


t = Operating temperature (in degrees Rankine)………….. {Parameter: <”Meter temperature”>} tc = Calibration temperature (in degrees Rankine)..………. {Parameter: <”Orifice cal temp”>}

Use: d' = ctt**dd ………………………..………...…….. OVC#4b

Where: d' = Cone outer diameter, corrected for expansion….…..… {Parameter: <“Corr orif diameter”>} d = Cone outer diameter (in metres), uncorrected……..….. {Parameter: <“Orifice diameter”>}


t = Operating temperature(in degrees Rankine)……….….. {Parameter: <”Meter temperature”>} tc = Calibration temperature (in degrees Rankine)…..……. {Parameter: <”Orifice cal temp”>}

Equation OVC#5: Velocity of approach

Use: E = 2V

D*Q*4

Where: E = Velocity of approach factor………………….….……… {Parameter: <”Orif vel of approach”>} D = Cone inner diameter, uncorrected for expansion..…. {Parameter: <“Pipe diameter”>}

And: VQ = 3600*Qm

Where: VQ = Volume rate (in m3/second)…………………………….{No Parameter}

mQ = Mass flow rate (in Kg/hour)……………………………. {See Equation OVC#1}

= Density of measured fluid (in Kg/m3).........…...…........{Parameter: <“Meter density”>}

Equation OVC#6: Reynolds number

Use: edR = *E*D

Where: edR = Reynolds number……………………………………….. {Parameter: <”Reynolds number”>}

E = Velocity of approach factor………………………..…… {See Equation OVC#5} D = Cone inner diameter, uncorrected for expansion..…. {Parameter: <“Pipe diameter”>}

= Dynamic viscosity………………………………………. {Parameter: <”Meter dynamic visc”>}


7951 2510 (Ch11/DD) Page 11.27


Equation OVC#7: Pressure ratio

Use: PR = 1

2PP

Where: PR = Pressure ratio...............................…………............... {Parameter: <“Pressure ratio”>}

1P = Pressure at up-stream tapping (in Bar)...…..……...... {No Parameter}

= 3Loss 10*PP

2P = Pressure at down-stream tapping (in Bar).……...…... {No Parameter} = PP1

And: P = Pressure measured at the metering-run……...…....... {Parameter: <“Meter pressure”>}

LossP = Pressure loss (in Bar)..........………..…...................... {Parameter: <“Pressure loss”>} = *25.13.1*P

Equation OVC#8: Mass rate ‘K factor’

Using: K = *P

Qm

Where: K = Mass flow rate ‘K’ factor........................…...……....... {Parameter: <“Mass rate k factor”>}

mQ = Mass flow rate (in Kg/hour)............……...…............... {Parameter: <“Mass rate”>}

P = Differential pressure (in Bar).......………….………..... {Parameter: <“Diff pressure value”>}

= Density of measured fluid (in Kg/m3).......………........ {Parameter: <“Meter density”>}

Equation OR9: Gross Volume flow rate

Using: GVQ =Meter

mQ

Where: GVQ = Gross Volume flow rate..………………………………..{Parameter: <”Gross vol rate”>}

mQ = Mass flow rate…………………………..………………. {Parameter: <”Mass rate”>}

Meter = Metering density……………………………...…………. {Parameter: <”Meter density”>}


Page 11.28 7951 2510 (Ch11/DD)

11.10 CORIOLIS FLOW METERING

Measurements and Features Supported:Mass flow rate - from a Coriolis mass flowmeter or mA/Hart Input Gross Volume flow rate Gross Standard Volume flow rate

Menu Navigation List:(1) <“Configure”>/<”Inputs”>/<“Flow meter”>, (2) <“Configure”>/<”Inputs”>/<“Flow meter”>/<”Coriolis meter”> (3) <“Configure”>/<“Flow rate”>, (4) <”Flow rates”>, (5) <“Density”>/<”Meter run density”> (6) <”Density”>/<”Base density”>



- Flow meter type 24 Error% / Kfactor 1 1 Mass rate input type E : : : :2 Mass rate HART chl A 33 Error% / Kfactor 10 3 Mass rate 0% value 34 Flowmeter K factor *4 Mass rate 100% value 35 Meter factor *5 HART mass rate fact B 36 Ind Mass Rate HI lmt C 6 Mass rate HI limit C 37 Ind Mass Rate LO lmt C 7 Mass rate LO limit C 38 Indicated mass rate 8 Mass rate * 39 Meter density * 9 Meter freq HI limit 40 Gross vol HI lmt C

10 Flow stop threshold 41 Gross vol LO lmt C 11 Meter freq * 42 Gross vol rate *12 Meter curve type G 43 Gross std vol HI lmt C 13 Meter curve points 44 Gross std vol LO lmt C 14 Flow/freq 1 45 Gross std vol rate *: : 46 CCF * D

23 Flow/freq 10 47 Base density * (D) 48 Flow rate action F

Notes are listed on the next page

Note: When a Coriolis meter is configured to output a frequency representing volume rather than mass, you must use the Turbine/PD Flow metering support.


7951 2510 (Ch11/DD) Page 11.29

CONFIGURATION CORIOLIS FLOW METERING

Notes: A Ensure that the basic configuration information of the live input channels has been completed.

Analogue Input…..….…… Turn to reference page 11.6 HART Input……….………. Turn to Chapter 17

B This factor location is for converting the Flow Computer scaled mass rate value into units of Kg per hour. By default, the factor has a value of 1.00; this setting assumes that the flowmeter converted the measured mass rate from units of Kg per hour into a mA value.

C Optional HI and LO alarm limits. Programming the limits with a zero value will avoid maximum and minimum alarm limit checks on the associated measurement.

D See “Volume Correction Factor” references in the Equation List section. [MENU(3)]

E A Coriolis mass flow meter is a resonating tube device that will distort proportionately to the rate of fluid mass flowing through it. The relationship of mass flow to the distortion for the meter is characterised to produce a k-factor in pulse/mass or mass/pulse units.

The signal output will generally be in the form of a pulse frequency signal, although a current 4-20mA output may also be available.

The Coriolis meter may also be configured to output a signal representative of volume. In this case the flow computer will handle the meter signal output in the same way as a single pulse input turbine signal. Unlike turbine signals ‘error checking’, (IP252), will not be carried out on the mass flow input signal. However, similar to the turbine linearisation, the flow computer allows the user to define a mass flow linearisation curve across a flow range. The curve will define the error deviation against flow or K-factor against frequency in terms of mass units. The linearisation calculation will automatically account for mass or volume type units based on the meter type selected by the user during configuration.

F By default, the 7951 calculates, for display purposes only, the actual live flow rates under a ‘Flow stopped’ condition, even when there is negligible flow. However, display can be forced to show zero flow by selecting the multiple-choice option with “Zero flow rates”. (Calculations using a flow rate will always use a zero value during a “Flow Stop” condition)

G There following calibration curve options for Coriolis flow metering are supported:

(1) Conversion (K v Hz)A ‘K-factor’ is interpolated, once during every machine cycle, from a user-programmable calibration curve. The ‘Meter factor’ (MF) is a fixed (SET) value. A SET MF value can still be updated by a proving session, by product detection, or by a MODBUS networked device. Also, see Figure 11.2 on page 11.10.

(2) Correction (% v flow”) (Default Option) The ‘Meter factor’ (MF) is calculated, once during every machine cycle, by a relative error (percentage) correction process. The ‘K-factor’ is a fixed (SET) value. They may then be updated by a proving session, by product detection or by a MODBUS networked device. Also, see page 11.11.

Proving sessions can overwrite either a ‘Meter factor’ value or the ‘K factor’ value. It is dependent on how proving is configured and if the prove session is successful. (See Chapter 16)

Product detection can also overwrite a ‘Meter factor’ (MF) value and/or the ‘K factor’ value.


Page 11.30 7951 2510 (Ch11/DD)

CORIOLIS FLOW METERING EQUATION LIST

Equation List:

Equation CFM#1: Gross Volume flow rate

Using: GVQ =Meter

mQ

Where: GVQ = Gross Volume flow rate…….……….……….. {Parameter: <”Gross volume rate”>}

mQ = Mass flow rate……………………...…………. {Parameter: <”Mass rate”>}

Meter = Metering density………………...……………. {Parameter: <”Meter density”>}

Equation CFM#2: Gross Standard Volume

Using: GSVQ = VCF*QGV

Where: SGVQ = Gross Standard Volume flow rate...……….. {Parameter: <”Gross std vol rate”>}

GVQ = Gross Volume flow rate..…………………….. {See Equation CFM#1}

VCF = Volume Correction Factor…………….…….. {See Equation CFM#3}

Equation CFM#3: Volume Correction Factor The equation used is dependent on the selected method for density referral - API Standard or 4x5 Matrix

Using: VCF = CPL*CTL …………………………….…….... (API)

Or: VCF = Base

Meter ...……………………………........... (4x5)

Where: VCF = Volume Correction Factor…………….…….. {Parameter: <”VCF”>}

CTL = Correction for temperature effects on fluid… {Parameter: <”CTL”>}

CPL = Correction for pressure effects on fluid…… {Parameter: <”CPL”>}

Meter = Metering density………………...……………. {Parameter: <”Meter density”>}

Base = Base density…………………….……………. {Parameter: <”Base density value”>}


7951 2510 (Ch11/DD) Page 11.31

11.11 Totalisers

7951 totalling features 3 basic types of incremental, roll-over counter:

Flow Total............... 5 x flow rate based totals for a metering-point. Each total is enabled by configuring the associated meter-run flow rate.

Alarm Total……...… 1 x user total for a metering-point. This is for totalling of either a flow rate or missing pulses from a dual pickup flowmeter. It increments only when there is an ‘active’ alarm.

Error Pulse Total…. 1 x error pulse total for a metering-point. This is for totalling of missing pulses from a dual pickup flowmeter. This totaliser function is permanently enabled.

Further separation of a total is made by the flow computer mode:

Normal mode (Standard) totalThis total is frozen whilst flow computer is in maintenance mode.

Maintenance mode totalThis total is frozen whilst the flow computer is in the normal operating mode.

Extra Information: (1) For information on configuring pulse output channels, turn to page 11.78. (2) Net Oil and Net ‘Water’ totalisers are shown on page 11.65.

Menu Navigation List:(1) <“Configure”>/<“Totalisation”>/<”Standard”> (2) <”Flow rates”> (3) <“Flow totals”>/<”Meter run totals”> (4) <“Health check”>/<“Totals”> (5) INFORMATION (‘i’-button) Menu

Parameter Lists: * shows data that can be “Live” or “Set”

Index Parameters Parameters Parameters Parameters Parameters ?

1 Indicated vol rate * Gross volume rate * Ind std vol rate * Gross std vol rate * Mass rate * A 2 Ind volume total Gross vol total Ind std vol total Gross std vol total Mass total 3 Ind vol increment Gross vol inc Ind std vol inc Gross std vol inc Mass increment 4 Ind vol rollover Gross vol rollover Ind std vol roll Gross std vol roll Mass rollover C5 Ind vol inhibit Gross vol inhibit Ind std vol inhibit Gross std vol inh Mass inhibit D6 Maint IV total Maint GV total Maint ISV total Maint GSV total Maint mass total 7 Maint IV inc Maint GV inc Maint ISV inc Maint GSV inc Maint mass inc


8 Alarm total src ptr 14 Main turb err roll C 9 Alarm increment 15 Maint turb error

10 Alarm total E 16 Maint turb err inc 11 Alarm rollover C 17 Operating mode G 12 Err pulse ip 1 value B - Flow status 13 Main turb errors B - Flow meter (A)

Figure 11.7: Totaliser Blocks and Parameters


Page 11.32 7951 2510 (Ch11/DD)

TOTALISERS CONFIGURATION

Notes:

A Indicated Volume measurements are not available when Orifice metering is selected.

B Missing (or error) pulses are not counted unless the volumetric pulse flowmeter has dual pick-ups wired to the Flow Computer and the pulse input channel is configured accordingly.

C By default, rollover (to zero) limits are pre-set to a very large number. However, it is advisable to check that the limits are sufficient for the metering application.

D This optional totaliser parameter is for freezing the flow total whilst there is an active alarm. Also, read note E.

E The alarm totaliser can be configured to continue totalling of a single parameter whilst there is an active alarm.

F An increment value is calculated by integrating a parameter value, e.g. flow rate, over time. The result is added to a corresponding total once during every machine cycle.

(a) Orifice or Coriolis Flow The time element of the increment calculation is the ‘actual cycle time’. This value is the elapsed time between a flow measurement. It is available for viewing from within the <“Time”> menu.

(b) Turbine Flow The time element of the increment calculation is the ‘pulse sample time’ – the period that pulses were accumulated for calculating the present value of the Indicated Volume flow rate. This time value is available for viewing within the <”Health check”> feature menu.

Editing an increment value has no effect.

G There are two flow computer modes to be aware of: 1. Normal-mode

In this mode, a standard total (e.g. “Ind volume total”) can increment. The corresponding maintenance-mode total (e.g. “Maint IV total”) will never increment.

2. Maintenance-modeIn this mode, a maintenance-mode total can increment. The corresponding standard total will never increment.

A mode can be selected only when the flow computer is in a ‘Flow Stopped’ state. For information on how the flow computer can be in a ‘flow stopped’ state, refer to the <”Flow status”> Parameter notes on the flow metering pages:

Turbine Flow.….. Page 11.9

Orifice Flow…..... Page 11.16

Coriolis Flow.….. Page 11.28


7951 2510 (Ch11/DD) Page 11.33

11.12 PRIME ‘DENSITY LOOP’ FLUID TEMPERATURE

Measurements Supported: (Also, see page 11.38 for use of these measurements.) ‘Density loop’ fluid temperature ‘A’ ‘Density’ loop fluid temperature ‘B’ Prime selected ‘density loop’ fluid temperature

Figure 11.8: Prime ‘Density Loop’ Temperature Blocks and Parameters

Menu Navigation List: (1) <“Configure”>/<“Temperature”>/<“Densitometer temp”>, (2) <“Temperature”>/<“Dens temperature”>, (3) <“Configure”>/<“Density”>/<”Header dens”>



1 Dens temp A source A 13 Dens temp B HI limit B 2 Dens temp A @ 100% 14 Dens temp B LO limit B 3 Dens temp A @ 0% 15 Dens tempB FB type C 4 Dens temp A HI lmt B 16 Dens tempB FB val C 5 Dens temp A LO lmt B 17 Dens temp B offset D 6 Dens temp A FB type C 18 Density B temp * 7 Dens temp A FB val C 19 Header txdr dens sel E, (F) 8 Dens temp A offset D 20 Prime dens temp * (F) 9 Density A temp * 21 Prime dens temp FB F 10 Dens temp B source 11 Dens temp B @ 100% 12 Dens temp B @ 0%

Notes: (X) – indirect reference in note X A Ensure that the basic configuration information of the live input channels has been completed.

Analog Input….….…… Turn to page 11.6 HART Input…………… Turn to Chapter 17

B Optional HI and LO alarm limits. Programming the limits with a zero value will avoid maximum and minimum alarm limit checks on the value of the associated measurement.

C Optional fallback facility is for the associated measurement.

D Optional parameter is for on-line correction to the LIVE associated measurement.

E See “Density” pages for use of this configuration parameter.

F Fallback value replaces the LIVE prime value when the prime density selection process (page 11.38) results in the fallback condition.


Page 11.34 7951 2510 (Ch11/DD)

11.13 PRIME ‘VISCOSITY LOOP’ FLUID TEMPERATURE

Measurements Supported: (Also, see page 11.52 for use of these measurements.) ‘Viscosity loop’ fluid temperature ‘A’ and temperature ‘B’. Prime ‘viscosity loop’ fluid temperature.

Figure 11.9: Prime 'Viscosity Loop' Temperature Blocks and Parameters

Parameter List: (1) <“Configure”>/<“Temperature”>/<“Viscometer temp”>, (2) <“Temperature”>/<“Visc temperature”> and (3) <“Configure”>/<“Viscosity”>/<“Header viscosity”>



1 Visc A temp source A 13 Visc B temp @ 0% 2 Visc A temp @ 100% 14 Visc B temp high lmt B 3 Visc A temp @ 0% 15 Visc B temp low lmt B 4 Visc A temp high lmt B 16 Visc B temp step lmt C 5 Visc A temp low lmt B 17 Visc B temp FB type D 6 Visc A temp step lmt C 18 Visc B temp FB value D 7 Visc A temp FB type D 19 Visc B temp offset 8 Visc A temp FB value D 20 Visc B temperature *9 Visc A temp offset 21 Header visc select F, (G) 10 Visc A temperature * 22 Prime visc temp * (G)11 Visc B temp source A 23 Prime visc temp FB G 12 Visc B temp @ 100%

Notes:A Ensure that the basic configuration information of the live input channels has been completed.

Analog Input……..…… Turn to page 11.6 HART Input…………… Turn to Chapter 17

B Optional HI and LO alarm limits. Programming the limits with a zero value will avoid maximum and minimum alarm limit checks on the associated measurement

C Optional alarm limit. Program it with a zero value to avoid a limit alarm check on the difference between two values of the associated parameter. Comparison values are from the present cycle and the previous cycle

D Optional fallback facility for the associated measurement

E Optional parameter for on-line correction to the LIVE associated measurement

F See “Viscosity” reference pages for use of this configuration parameter.

G Fallback value replaces the LIVE prime value when the prime viscosity selection process (page 11.38) results in a fallback condition.


7951 2510 (Ch11/DD) Page 11.35

11.14 METER TEMPERATURE

Measurement Supported: (Also, see pages 11.44 - 45 for use of meter temperature.) Fluid temperature at the metering point.

Figure 11.10: Metering Temperature Blocks and Parameters

Parameter List: (1) <“Configure”>/<“Temperature”>/<“Meter temperature”> and (2) <“Temperature”>/<“Meter run temp”>



1 Meter temp input chl A 6 Meter temp LO limit B 2 Meter temp @ 100% 7 Meter temp step lmt C 3 Meter temp @ 0% 8 Meter temp FB type D 4 Meter temp offset E 9 Meter temp FB value D 5 Meter temp HI limit B 10 Meter temperature *



B Optional HI and LO alarm limits. Programming the limit with a zero value will avoid maximum and minimum alarm limit checks on the associated measurement.

C Optional alarm limit. Program it with a zero value to avoid a limit alarm check on the difference between two values of the associated parameter. Comparison values are from the present cycle and the previous cycle.

D Optional fallback facility for the associated measurement.

E Optional parameter for on-line correction to the LIVE associated measurement.


Page 11.36 7951 2510 (Ch11/DD)

11.15 ‘DENSITY LOOP’ PRESSURE

Measurement Supported: ‘Density loop’ pressure.

Figure 11.11: 'Density Loop' Pressure Blocks and Parameters

Parameter List: (1) <“Configure”>/<“Pressure”>/<“Header pressure”> and (2) <“Pressure”>/<“Dens pressure”>



1 Density pressure src A 6 Dens press step lmt C 2 Dens press 100% val 7 Dens press FB type D 3 Dens press 0% val 8 Dens press FB val (D) 4 Dens press HI lmt B 9 Density pressure * 5 Dens press LO lmt B

Notes:A Ensure that the basic configuration information of the live input channel has been completed


B Optional HI and LO alarm limits. Programming the limits with a zero value will avoid maximum and minimum alarm limit checks on the associated measurement

C Optional alarm limit. Program it with a zero value to avoid a limit alarm check on the difference between two values of the associated parameter. Comparison values are from the present cycle and the previous cycle



7951 2510 (Ch11/DD) Page 11.37

11.16 METER PRESSURE

Measurement Supported: Pressure at the metering point

Figure 11.12: Metering Pressure Blocks and Parameters

Parameter List: (1) <“Configure”>/<“Pressure”>/<“Meter run pressure”> and (2) <“Pressure”>/<“Meter run pressure”>



1 Meter press source A 6 Meter press step lmt C 2 Meter press 100% val 7 Meter press FB type D 3 Meter press 0% val 8 Meter press FB val (D) 4 Meter press HI lmt B 9 Meter pressure * 5 Meter press LO lmt B


Analog Input….….…… Turn to page 11.6 HART Input…………… Turn to Chapter 17

B Optional HI and LO alarm limits. Programming the limits with a zero value will avoid maximum and minimum alarm limit checks on the associated measurement.

C Optional alarm limit. Program it with a zero value to avoid a limit alarm check on the difference between two values of the associated parameter. Comparison values are from the present cycle and the previous cycle.



Page 11.38 7951 2510 (Ch11/DD)

11.17 HEADER DENSITY Measurements Supported: (Note: These measurements are also available when measuring viscosity.) Density ‘A’ – from liquid density transducer or a 7827 5 viscosity analyser) Density ‘B’ – from liquid density transducer, a 7827 viscosity analyser, mA Input, HART Input, or FC-BASIC

Prime selected density – from Density ‘A’ or ‘B’ or Fallback facility)

Menu Navigation List: (1) <“Configure”>/<“Transducer details”>, (2) <“Health check”>/<”Inputs”>/<“Time period inputs”>, (3) <“Configure”>/<“Density”>/<“Header dens”> and (4) <“Density”>/<“Header density”>


Index Parameters Notes? Index Parameters Notes? 1a Time period input 1 * A 21a Time period input 2 * 1b Time period input 1b * A 21b Time period input 2b * 2 Time period 1 type A 22 Time period 2 type 3 Dens 1 glitch limit 23 Dens 2 glitch limit 4 Dens meter 1 K0 24 Dens meter 2 K0 5 Dens meter 1 K1 25 Dens meter 2 K1 6 Dens meter 1 K2 26 Dens meter 2 K2 7 Density 1 correct C 27 Density 2 correct C 8 Dens meter 1 K18 28 Dens meter 2 K18 9 Dens meter 1 K19 29 Dens meter 2 K19

10 Dens meter 1 K20a 30 Dens meter 2 K20a 11 Dens meter 1 K20b 31 Dens meter 2 K20b 12 Dens meter 1 K21a 32 Dens meter 2 K21a 13 Dens meter 1 K21b 33 Dens meter 2 K21b 14 Dens meter 1 type C 34 Dens meter 2 type C 15 Dens meter 1 VOS 35 Dens meter 2 VOS 16 Dens meter 1 offset 36 Dens meter 2 offset 17 Dens meter 1 factor 37 Dens meter 2 factor 18 Density A value * 38 DensB Ain/HART src F 19 Header den comp lmt B 39 Density B @ 100% 20 Density B calc sel H 40 Density B @ 100%

5 The 7827 does not measure fluid density as accurately as a 783x or 784x liquid density transducer. Density measurements from a

7827 also require a correction for viscosity effects if the fluid viscosity exceeds 100cP.


7951 2510 (Ch11/DD) Page 11.39

CONFIGURATION HEADER DENSITY

(Parameter list continued…) * shows data that can be “Live” or “Set”

Index Parameters Notes? Index Parameters Notes? 41 Density B value * 47 Header density * 42 Header txdr dens sel D 48 Head analog dens * G 43 Density HI limit E tA Density A temp * 44 Density LO limit E tB Density B temp * 45 Header dens FB type PDensity Density pressure * 46 Header dens FB val

Notes:A The “Density” option (value) is for when the density ‘A’ measurement involves a liquid density transducer.

Live transducer values will appear in the <“Time period Input 1”> parameter (location).

The “7827” option (value) is for when the density ‘A’ measurement involves a 7827 viscosity analyser. Live 7827 values will appear in the <“Time Period Input 1b”> parameter (location) instead of the <“Time Period Input 1”> parameter (location).

(Chapter 2 features time period input and analogue input rear panel connections)

B This alarm limit checking can be switched off by setting a large enough density value that will always greater than the difference between density ‘A’ and density ‘B’ measurements.

C Various combinations of corrections to density can be selected, as shown in Table 11.5. Table 11.6 then shows the availability of selected corrections when using different types of transducer.

D Select a logic table to be used by the Flow Computer to perform prime header density channel re-selection. (For details, turn to the “Prime Header Density Re-selection Procedure” section on page 11.37)

E High and low alarm limits are applied to the selected prime density value. These limits are not checked when both limits are programmed (SET) to zero.

F Ensure that the basic configuration information of the live input channel has been completed. Analogue Input….…… Turn to page 11.6 HART Input…………… Turn to Chapter 16

G This measurement can be used by the Product Detection feature. (See “Interface Detection” page 11.74)

H When FC-BASIC is selected, Density B is updated from a FC-BASIC script. (See Chapter 18 about FC-BASIC)

Table 11.5: Options for selecting corrections

Option Descriptor (as displayed)

Correction: Temperature

Correction: Pressure

Correction: VOS

Correction: Viscosity

NoneTempPressVOS Temp press Temp VOS Press VOS Temp press VOS

Table 11.6: Availability of Corrections to Density (by transducer)

Transducer Type

Temperature Effects

Pressure Effects

Viscosity Effects

VOS Effects

7827783x/784x

1762


Page 11.40 7951 2510 (Ch11/DD)

HEADER DENSITY CONFIGURATION

Prime Header Density Re-Selection Procedure In the event of a density input channel (e.g. density ‘A’) failing or returning to a live state, the Flow Computer will perform a re-selection procedure for obtaining a prime density value from an alternative source. This procedure involves evaluating a user-selected logic decision table to determine where now to get the prime value.

Table 11.7: Logic table for the “Automatic A” configuration option. (Density ‘A’ is preferred)

Key:A = Density ‘A’, B = Density ‘B’, FB = Fallback

Notes:1. The “Automatic B” configuration option uses the same logic table except Density ‘B’ is the preferred channel. This preference reverses the A and B selection in the last column of this table.

2. “Out of limit” columns 1 and 2 are concerned with the HI or LO alarm limits.

3. “Input failed” columns are concerned with ‘Live’ inputs.

Table 11.8: Logic table for the “Density A”configuration option

Key: - A = Density ‘A’, B = Density ‘B’, FB = Fallback

Table 11.9: Logic table for the “Density B”configuration option

Key: - A = Density ‘A’, B = Density ‘B’, FB = Fallback

Density ‘A’ Out of Limit

Density ‘B’ Out of Limit

A#B (Comp) Out of Limit

Density ‘A’ InputFailed

Density ‘B’ InputFailed

Density Selected

Yes Yes Yes No No FB No Yes Yes No No A Yes No Yes No No B No No Yes No No B Yes Yes No No No A No Yes No No No A Yes No No No No B No No No No No A Yes Yes Yes Yes No FB No Yes Yes Yes No FB Yes No Yes Yes No B No No Yes Yes No B Yes Yes No Yes No B No Yes No Yes No FB Yes No No Yes No B No No No Yes No B Yes Yes Yes No Yes FBNo Yes Yes No Yes AYes No Yes No Yes FBNo No Yes No Yes AYes Yes No No Yes FBNo Yes No No Yes AYes No No No Yes FBNo No No No Yes AYes Yes Yes Yes Yes FBNo Yes Yes Yes Yes FBYes No Yes Yes Yes FBNo No Yes Yes Yes FBYes Yes No Yes Yes FBNo Yes No Yes Yes FBYes No No Yes Yes FBNo No No Yes Yes FB

Density ‘A’ Out of Limit

Density ‘A’ Input Failed

Prime Density Selected

No No A No Yes FBYes No FB Yes Yes FB

Density ‘B’ Out of Limit

Density ‘B’ Input Failed

Prime Density Selected

No No B No Yes FBYes No FB Yes Yes FB


7951 2510 (Ch11/DD) Page 11.41

EQUATION LIST HEADER DENSITY

Density Equation List (Parameters listed are for channel ‘A’. Parameters for channel ‘B’ are shown on page 11.38).

IMPORTANT NOTICE

Density measurements from a 7827 are supported. However, the density corrections for viscosity effects and VOS effects are not yet available in software version 2510.

The viscosity effect correction is normally required for fluids with a viscosity that exceeds 100cP.

For further information on these corrections, refer to the 7827 Technical Manual.

Equation DE#1a: Uncorrected density from a 783x/784x liquid density transducer

Using: u =2

210 *K*KK

Where: u = Density (uncorrected)………………………………………. Parameter: <”Density A”>

0K = Transducer calibration factor K0……………………………Parameter: <”Density1 K0”>



= Periodic time from transducer ( s)………………………... Parameter: <”Time Period Input 1”>

Equation DE#1b: Uncorrected density from a 7827 liquid viscosity transducer

Using: u =2B2B10 *K*KK

Where: u = Density (uncorrected)………………………………………. Parameter: <”Density A”>

0K = Transducer calibration factor K0…………………………... Parameter: <”Density1 K0”>

1K = Transducer calibration factor K1………………….……….. Parameter: <”Density1 K1”>

2K = Transducer calibration factor K2….……………………......Parameter: <”Density1 K2”>

B = Periodic time from transducer ( s)………………………... Parameter: <”Time Period Input 1b”>

Equation DE#2: Density corrected for temperature effects This equation corrects a density measurement for the temperature effect on the metalwork of the transducer when operated away from the calibration temperature.

Using: t = b19b18u tt*Ktt*K1*

Where: t = New density (temperature corrected)…………….…….… Parameter: <”Density A”>

u = Density without temperature correction…………………... Parameter: <”Density A”>

18K = Transducer calibration factor K18……………………….....Parameter: <”Density1 K18”>

19K = Transducer calibration factor K19…….…………………… Parameter: <”Density1 K19”>

t = ‘Density loop’ temperature…………..………………….…. Parameter: <”Density A temp”>

bt = Transducer calibration temperature (always 20 C)...…… (Not displayed in menu)


Page 11.42 7951 2510 (Ch11/DD)

HEADER DENSITY EQUATION LIST

Note: Parameters listed are for channel ‘A’. Parameters for channel ‘B’ are on page 11.38.

Equation DE#3: Density corrected for pressure effects This equation corrects a density measurement for the pressure effect on the metalwork of the transducer when operated away from the calibration pressure.

Using: P = b21b20 PP*KPP*K1*

Where: P = New density (pressure corrected)…….………………… Parameter: <”Density A”>

= Density without pressure correction……………..…...… Parameter: <”Density A”> P = ‘Density loop’ pressure…………….……………….……. Parameter: <”Header dens press”>

bP = Transducer calibration pressure (always 1 bar Abs.).… (Not displayed in menu)

And: 20K = BB20A20 PP*KK ……………………...…………(Not displayed in menu)

21K = BB21A21 PP*KK …………………………………(Not displayed in menu)

Where: A20K = Transducer calibration factor K20A……………..………..Parameter: <”Density1 K20a”>

B20K = Transducer calibration factor K20B……………..………..Parameter: <”Density1 K20b”>

A21K = Transducer calibration factor K21A……………..………..Parameter: <”Density1 K21a”>

B21K = Transducer calibration factor K21B………………..……..Parameter: <”Density1 K21b”>

Equation DE#4: Density corrected for VOS effects [NOT AVAILABLE TO 7827 USERS] This equation corrects a density measurement for the VOS effect of the measured liquid compared to the VOS effect on the calibration liquid at the same conditions.

Using: v = 2

Avos

2

Cvos

VOS*K1

VOS*K1

*

Where: v = New density with VOS correction………..……………… Parameter: <”Density A”>

= Density without VOS correction………..……………….. Parameter: <”Density A”> = Periodic time from transducer ( s)……………………... Parameter: <”Time Period Input 1”>

AVOS = VOS (velocity of sound) of measured liquid…………… Parameter: <” Density1 VOS”>

CVOS = VOS (velocity of sound) of calibration liquid.………….. See Equation DE#5

vosK = Value automatically selected from a built-in table…….. (Not displayed in menu)

Table 11.10: KVOS values for Equation DE#4

Transducer KVOS

1762 28500

7830/7840 35900 7835/7845 19800

7826 67800


7951 2510 (Ch11/DD) Page 11.43

EQUATION LIST HEADER DENSITY

Note: Parameters listed are for channel ‘A’. Parameters for channel ‘B’ are on page 11.38.

Equation DE#5: VOS (velocity of sound) effects of calibration fluid This equation is for generating a factor for the VOS effect on the calibration liquid under present flow conditions. It is used in association with Equation DE#4.

Using: CVOS =3

4vos2

3vos2vos1vos *K*K*KK

Where: CVOS = New VOS (velocity of sound) of calibration fluid……….... (Not displayed in menu)

= Density without VOS correction……………………..……. Parameter: <”Density A”>

1vosK = Value from column 2 of Table 11.11………….………… (Not displayed in menu)




Table 11.11: KVOS values for Equation DE#5

Transducer KVOS1 KVOS2 KVOS3 KVOS4

1762 1157 0 0 0.000000343

7830/7840 214.91 0.15941 0.0025398 -0.0000014169 7835/7845 214.91 0.15941 0.0025398 -0.0000014169

7826 230.915 0.126713 0.00255082 -0.0000014164


Page 11.44 7951 2510 (Ch11/DD)

11.18 API REFERRED DENSITY

Measurements Supported: (Note: The alternative density referral method is on page 11.45) Base density by API referral calculation Meter density direct from prime density or by API referral calculation

API Standard Compliance(1) General Crude Oil API Std 2540, Chapter 11.1 Tables 23A & 24A, 53A & 54A (SG range is 0.6610 to 1.076) (2) General Products API Std 2540, Chapter 11.1 Tables 23B & 24B, 53B & 54B (SG range is 0.6535 to 1.076) (3) User-defined K0, K1 API Std 2540, Chapter 11.1 Tables 24C, 54C

Figure 11.13: API Referred Density Blocks and Parameters

Menu Navigation List: (1) <“Configure”>/<“Density”>, (2) <“Configure”>/<“Base density”>, (3) <“Density”>, (4) <“Base density”> (5) <“Temperature”> and (6) <“Pressure”>



1 Header density * E 15 CTL 2 Dens calc sel D 16 CPL 3 Dens Base temp cond 17 API compress F b->m 4 Base press value 18 API alpha b->m 5 Equilibrium press 19 Meter dens/visc sel C 6 API product select 20 Meter density * 7 API range select 21 Base dens HI limit 8 API User K0 22 Base dens LO limit 9 API User K1 23 Meter temperature *

10 Base density value * 24 Prime dens temp * A 11 CTLd 25 Density pressure * B 12 CPLd 26 Meter pressure * 13 API alpha d->b 14 API compress F d->b

Notes:

A See “Prime Density Loop Fluid Temperature” reference pages, starting with page 11.33.

B See “Density Loop Pressure” reference pages, starting with page 11.36.

C Select the “Calculation” option descriptor unless your intention is to by-pass the referral calculations.

D This parameter allows the selection of a density referral standard. (Select the “API” option). [MENU(2)]

E Referral calculations require prime density to be within the range of 350 to 1074 Kg/m3


7951 2510 (Ch11/DD) Page 11.45

11.19 4X5 MATRIX REFERRED DENSITY

Measurements Supported: (Note: The alternative density referral method is on page 11.44) Base density by referral calculation Meter density direct from prime density or by referral calculation

Figure 11.14: 4x5 Matrix Referred Density Blocks and Parameters




1 Header density * 21 Density matrix R31 2 Dens calc sel D 22 Density matrix R32 3 Density matrix T0 23 Density matrix R33 4 Density matrix T1 24 Density matrix R40 5 Density matrix T2 25 Density matrix R41 6 Density matrix T3 26 Density matrix R42 7 Density matrix T4 27 Density matrix R43 8 Density matrix R00 28 Density K40 9 Density matrix R01 29 Density K41

10 Density matrix R02 30 Base density value *11 Density matrix R03 31 Base dens HI limit 12 Density matrix R10 32 Base dens LO limit 13 Density matrix R11 33 Meter dens/visc sel C 14 Density matrix R12 34 Meter density *15 Density matrix R13 35 Dens Base temp cond 16 Density matrix R20 36 Base press value 17 Density matrix R21 37 Meter temperature *18 Density matrix R22 38 Prime dens temp * A19 Density matrix R23 39 Density pressure * B20 Density matrix R30 40 Meter pressure *

Notes:A See “Prime Density Loop Fluid Temperature” reference pages, starting with page 11.33.

B See “Density Loop Pressure” reference pages, starting with page 11.36.

C Select the “Calculation” option descriptor unless your intention is to by-pass the referral calculations.

D This parameter allows the selection of a density referral standard. (Select the “4x5 Matrix” option). [MENU(2)]


Page 11.46 7951 2510 (Ch11/DD)

11.20 METER DENSITY OF KNOWN FLUID

Measurements Supported: (For the equivalent meter density measurement, see the next page). Base Density of a known fluid by referral calculation

Figure 11.15: Known Fluid Base Density Blocks and Parameters




1 Header dens * (E) 7 Equilibrium press MENU(6)2 Meter dens/visc sel C 8 Base dens method D 3 Base temperature MENU(5) 9 Base dens HI limit 4 Base press value MENU(6) 10 Base dens LO limit 5 Prime dens temp * A 11 Base density value *6 Density pressure * B

Notes:

A Observed temperature. See configuration reference page 11.33

B Observed pressure. See configuration reference page 11.36

C Select the “Calculation” option (value) unless there is a need to by-pass the density referral calculations. [MENU(3)]

D Select a referral calculation for each metering-point. [MENU(2)]

E API (Std 2540) referral is performed for a generalised product where the Header density is within the range of 350 to 1074 Kg/m3. (Header density information starts on page 11.38).

Standards ComplianceNGL/LPG GPA Technical Publication TP25, Tables 24E & 23E (SG range is 0.495 to 0.637) Ethylene IUPAC Ethylene API 2565 Chapter 11.3.2.1 Propylene API 2565 Chapter 11.3.3.2


7951 2510 (Ch11/DD) Page 11.47

11.21 BASE DENSITY OF KNOWN FLUID

Measurements supported: (For the equivalent base density measurement, see previous page.) Meter Density of a known fluid - direct from Header or by referral calculation

Figure 11.16: Meter Density - Known Fluid - Blocks and Parameters (1x4x1)




1 Base density * (E) 6 Meter pressure * B2 Dens Base temp cond MENU(5) 7 Base dens method D 3 Base press value MENU(6) 8 Meter dens/visc sel C 4 Equilibrium press MENU(6) 9 Meter density *5 Meter temperature * A

Notes:

A Observed temperature. See configuration reference page 11.33.

B Observed pressure. See configuration reference page 11.36.

C Select the “Calculation” option (value) when using density referral calculation.

D Select a referral calculation for each metering-point. [MENU(2)]

E API (Std 2540) referral is performed for a generalised product where the Header density is within the range of 350 to 1074 Kg/m3. (Base density information starts on page 11.46)

Standards ComplianceNGL/LPG GPA Technical Publication TP25, Tables 24E & 23E (SG range is 0.495 to 0.637) Ethylene IUPAC Ethylene API 2565 Chapter 11.3.2.1 Propylene API 2565 Chapter 11.3.3.2


Page 11.48 7951 2510 (Ch11/DD)

11.22 SPECIFIC GRAVITY / DEGREES API

Measurement Supported: Specific gravity for the measured fluid

Equation DE#6: Specific gravity of measured fluid

Using: SG =Water

Base

Where: SG = Specific gravity of measured fluid

Base = Base density of measured fluid

Water = Base density of water

Menu Navigation List: (1) <“Configure”>/<“Specific gravity”> and (2) <“Density”>/<”Base density”>



1 Base density value * A 4 SG HI limit C 2 Water density (SG) * B 5 SG LO limit C 3 SG value *

Notes:

A Turn to pages 11.44 - 45 for base density measurement support.

B Turn to “Net Oil/Net Water” reference pages for details.

C Optional alarm limits for specific gravity values.

Measurement Supported: Degrees API for measured fluid

Equation DE#7: Degrees API for measured fluid

Using: API = 5.131SG

5.141

Where: API = Degrees API SG = Specific gravity

Menu Navigation List: (1) <“Density”><”Degrees API”> and (2) <“Configure”>/<“Specific gravity”>



1 Degrees API * 2 SG value *

Notes:(Nothing Applicable)


7951 2510 (Ch11/DD) Page 11.49

11.23 SPECIAL EQUATIONS

Feature: Special Equation Type One

Although this special equation can be used for any purpose, the typical application is for calculating, for example, Degrees Brix for non-linear products.

Equation SPE#1: Special Equation Type One

Using: f*Ye*d)c*Xb*aBAR

Where: A, B = Constants a - f = Pointers X. Y = Constants R = Result


(1) <“Configure”>/<“Special equations”>


Term Parameter (as displayed) Notes? Term Parameter (as displayed) Notes?

R Special equation 1 * N/A General constant 1 C A Special eq 1 const A N/A General constant 2 C B Special eq 1 const B N/A General constant 3 C X Special eq 1 const X N/A General constant 4 C Y Special eq 1 const Y a Special eq 1 ptr a B b Special eq 1 ptr b B c Special eq 1 ptr c B d Special eq 1 ptr d B e Special eq 1 ptr e B f Special eq 1 ptr f B

N/A Special eq 1 name A

Notes:

A A facility is provided whereby a text title can be edited to give the calculation a meaningful name. Changing the default text will alter the on-screen description of the parameter for term R.

B Edit the value with the identification number of the parameter to be used for this term. Identification numbers can be seen on-screen by locating the data in the menu system and then pressing the ‘a’-button. Re-press the ‘a’-button to remove the number from the display. With this type of parameter, the word “Off” is seen when not in use.

C There is a collection of unused data locations within the custom equation menu. These are provided for defining constants that could be identified as equation terms ‘a’, ‘b’, etc.


Page 11.50 7951 2510 (Ch11/DD)

11.24 HEADER ‘VISCOSITY LOOP’ DENSITY

Measurements Supported: (Note: These measurements are available only when measuring viscosity) ‘Viscosity loop’ Fluid Density ‘A’ (direct from a 7827 6 viscosity analyser) ‘Viscosity loop’ Fluid Density ‘B’ (direct from a 7827 viscosity analyser) Header ‘viscosity loop’ density (from density ‘A’ or ‘B’ or fallback)

Figure 11.17: Viscosity Density Blocks and Parameters

Menu Navigation List: (1) <“Configure”>/<“Transducer details”>/<”Viscometer 3”>/<”Density data”> and <”Viscometer 4”>/<”Density data”> (2) <“Health check”>/<”Inputs”>/<“Time period inputs”>, (3) <“Configure”>/<“Density”>/<”Header visc dens”>, (4) <“Density”>, (5) <“Temperature”> and (6) <“Pressure”>


Index Parameters Notes? Index Parameters Notes? 1 Time period input 3b * A 13 Time period input 4b * B 2 Visc meter A K0 14 Visc meter B K0 3 Visc meter A K1 15 Visc meter B K1 4 Visc meter A K2 16 Visc meter B K2 5 Visc meter A correct E 17 Visc meter B correct E 6 Visc meter A K18 18 Visc meter B K18 7 Visc meter A K19 19 Visc meter B K19 8 Density3 txdr type 20 Density4 txdr type 9 Visc meter A VOS D 21 Visc meter B VOS D

10 Visc meter A offset 22 Visc meter B offset 11 Visc meter A factor 23 Visc meter B factor 12 Visc A Density * 24 Visc B Density *

tA (Visc) Visc A temperature * TB (Visc) Visc B temperature * 25 Header visc select C 26 Visc header density *

Notes: A Live periodic time values, representing fluid density, from a connected 7827 viscosity transducer appear in the

<“Time Period Input 3b”> parameter (location) instead of <“Time Period Input 3”>.

B Live periodic time values, representing fluid density, from a connected 7827 viscosity transducer appear in the <“Time Period Input 4b”> parameter (location) instead of <“Time Period Input 4”>.

C This parameter is also used when configuring the prime selection of header viscosity measurements. [MENU(3)]Refer to Table 11.14 on page 11.51 for the selection logic of header ‘viscosity loop’ density.

6 The 7827 does not measure fluid density as accurately as a 783x or 784x liquid density transducer. Density measurements from a

7827 may require a correction for viscosity effects if the fluid viscosity is in excess of 100cP.


7951 2510 (Ch11/DD) Page 11.51

CONFIGURATION HEADER ‘VISCOSITY LOOP’ DENSITY

(Notes continued…)

D Optional correction to density. A value for the VOS effect has to be programmed into the Flow Computer. For information about velocity of sound effects on fluid density measurements, refer to the handbook supplied with the transducer.

E Various combinations of corrections to density can be selected and applied, as shown in Table 11.12. Table 11.13 then shows the suitability of corrections when using the 7827.

Table 11.12: Viscosity Loop Density Correction Options

Option Descriptor

(as displayed)Correction:

TemperatureCorrection:

VOSCorrection:

Pressure Correction: Viscosity

None

Temp

Press

VOS

Temp press

Temp VOS

Press VOS

Temp press VOS

Table 11.13: Applicable Corrections to Density from a 7827

Transducer Type

Temperature Effects

Viscosity Effects

VOS Effects

7827

Table 11.14: Logic table for Prime Viscosity Density Selection

Prime Selection: Header Viscosity *

Visc Density ‘A’ Live Input Fail ?

Visc Density ‘B’ Live Input Fail ?

Header ‘Viscosity Loop’ Density

“Viscosity A” No No C “Viscosity A” No Yes C “Viscosity A” Yes No FAIL “Viscosity A” Yes Yes FAIL “Viscosity B” No No D “Viscosity B” No Yes FAIL “Viscosity B” Yes No D “Viscosity B” Yes Yes FAIL

Fallback No No FB Fallback No Yes FB Fallback Yes No FB Fallback Yes Yes FB

“C” = Density ‘C’ (Viscosity density channel ‘A’) “D” = Density ‘D’ (Viscosity density channel ‘B’)

“FAIL” = No Alternative Source FB = Fallback

* Monitor selection by viewing <”Header Dyn visc sel”> parameter


Page 11.52 7951 2510 (Ch11/DD)

11.25 HEADER VISCOSITY

Measurements: (Note: These measurements are also available whilst measuring ‘viscosity loop’ density.) Dynamic Viscosity ‘A’ & ‘B’, Header dynamic viscosity. Kinematic Viscosity ‘A’ & ‘B’, Header kinematic viscosity.

Figure 11.18: Header Viscosity Blocks and Parameters

Menu Navigation List: (1) <“Health Check”>/<“Inputs”>/<”Time period inputs”>, (2) <“Configure”>/<“Transducer details”>, (3) <“Configure”>/<“Viscosity”>/<”Header viscosity”>, (4) <“Viscosity”>/<”Header viscosity”>


Index Parameters Notes? Index Parameters Notes? 1 Time period input 3 * 30 Time period input 4 *2 Time period input 3b * 31 Time period input 4b *3 Q factor visc A * 32 Q factor visc B * 4 Visc A calib ranges 33 Visc B calib ranges 5 Visc A ultra-low V0 34 Visc B ultra-low V0 6 Visc A ultra-low V1 35 Visc B ultra-low V1 7 Visc A ultra-low V2 36 Visc B ultra-low V2 8 Visc A u-low scale 37 Visc B u-low scale 9 Visc A low V0 38 Visc B low V0 10 Visc A low V1 39 Visc B low V1 11 Visc A low V2 40 Visc B low V2 12 Visc A low scale 41 Visc B low scale 13 Visc A medium V0 42 Visc B medium V0 14 Visc A medium V1 43 Visc B medium V1 15 Visc A medium V2 44 Visc B medium V2 16 Visc A medium scale 45 Visc B medium scale 17 Visc A high V0 46 Visc B high V0 18 Visc A high V1 47 Visc B high V1 19 Visc A high V2 48 Visc B high V2 20 Visc A high scale 49 Visc B high scale 21 Visc A Hysteresis B 50 Visc B Hysteresis B 22 Visc A ultra-low lmt 51 Visc B U-low limit 23 Visc A UL-L switch 52 Visc B UL-L switch 24 Visc A L-M switch 53 Visc B L-M switch 25 Visc A M-H switch 54 Visc B M-H switch 26 Visc A high range 55 Visc B high range 27 Dynamic visc A * 56 Dynamic visc B *28 Visc A current range 57 Visc B current range 29 Visc glitch filter 58 Dyn visc comp limit


7951 2510 (Ch11/DD) Page 11.53

CONFIGURATION HEADER VISCOSITY

(Parameter List continued…) * shows data that can be “Live” or “Set”

Index Parameters Notes? Index Parameters Notes? 59 Dyn visc HI limit 66 Visc header density *60 Dyn visc LO limit 67 Kinematic visc A *61 Kin visc HI limit 68 Kinematic visc B *62 Kin visc LO limit 69 Header visc select A 63 Viscosity FB type 70 Header kin visc *64 Dyn visc FB value 71 Header dynamic visc *65 Kin visc FB value 72 Header Dyn visc sel

Notes:A The selected option also controls the prime selection of a ‘viscosity loop’ density measurement channel.

B A brief guide to the Hysteresis mechanism is shown below.

Hysteresis Guide The Flow Computer can use hysteresis to select a calibrated range for the transducer; even if programmed ranges have some overlap. Range identification, even without use of hysteresis, allows the Flow Computer to use the most appropriate set of factors for calculations. The V0, V1 and V2 factors for each calibrated range are found on the transducer certificate. For further information on calibration ranges, refer to the Technical Manual that was supplied with the transducer. Hysteresis also avoids continuous switching between calibration ranges when the dynamic viscosity is fluctuating around a calibration range boundary.

Example: Calibration Range Identification Consider 1% hysteresis with Viscosity Transducer ‘A’ calibrated for low, medium and high ranges. Work through the numbered calculations with reference to the diagram and table of configuration details associated with hysteresis.

Parameters Value/Option Ref. Calculated Boundary Values

Visc A ultra-low lmt 1 cP - - Visc A UL-L switch 10 cP SD 9.9 cP, 10.1 cP Visc A L-M switch 100 cP SC 99 cP, 101 cP Visc A M-H switch 1000 cP SB 990 cP, 1010 cP Visc A high range 12500 cP SA - Visc A calib ranges low, med,high - - Visc A hysteresis 1% - -

Calculations:

1 Hysteresis boundary point calculations for switching between the medium and high calibration ranges.

10011*1 BSA

10011*1 BSB

99.0*10001A )01.1(*10001B

9901A 10101B

Results Switch to high range from medium range at just over 1010 cP. Switch to medium range from high range at just under 990 cP.

High RangeA1

B1

DynamicViscosity

(cP)

CalculatedHysteresis

PointsSC

SA

No Calibration Range (Fail)

B2

A2

Medium Range

Hysteresis Band

Hysteresis Band

SB

Low Range

No Calibration Range (Fail)SD

A Zone HysteresisHigh * 1

100

B Zone HysteresisLow * 1

100


Page 11.54 7951 2510 (Ch11/DD)

CONFIGURATION HEADER VISCOSITY

2 Hysteresis point calculations for switching between medium and low viscosity calibration ranges.

10011*2 CSA

10011*2 CSB

99.0*1002A 01.1*1002B

992A 1012B

Results Switch to medium range from low range at just over 101 cP. Switch to low range from medium range at just under 99 cP.

3 Hysteresis point calculations for changes switching low and ultra-low viscosity calibration ranges: Without an ultra-low calibration range set-up, dynamic viscosity ‘A’ data shows “Fail” on the status line when the calculated value goes below 9.9 cP. The low range remains selected. Once a fail status is shown, dynamic viscosity ‘A’ must go above 10.1 cP to become “Live”.

4 Hysteresis point calculations for changes around the upper limit of the high viscosity calibration range: The dynamic viscosity ‘A’ parameter shows “Fail” on the status line when the calculated value goes above the high limit - 12,500 cP in the example. The high range remains selected. Once a “fail” status is shown, the dynamic viscosity ‘A’ measurement value must fall below the high limit (12,500 cP) to become “Live” again.

Viscosity Equation List: (Note: Parameters shown are for the viscosity measurement channel ‘A’. For channel ‘B’ parameters, see page 11.52)

Equation VISC#1: Quality factor from a 7827 liquid viscosity analyser

Using: Q =5.0

AB

5.0

BA

1

Where: Q = Quality factor of transducer (no units)….……...……... {Parameter: <”Q factor visc A”>}

A = Time period ‘A’ of 7827 (�s)………..….….….……...…{Parameter: <”Time period input 3”>}

B = Time period ‘B’ of 7827 (�s)………..….…….……..…. {Parameter: <”Time period input 3b”>}

Equation VISC#2: Fluid dynamic viscosity

Using: = 42210

Q

1*VQ

1*VV

Where: = Fluid dynamic viscosity (cP)……………………………. {Parameter: <”Dynamic visc A”>}

0V = 7827 calibration factor V0……..…………...……………{Parameter: <Visc A xxx V0>} *

1V = 7827 calibration factor V1…………….………………… {Parameter: <Visc A xxx V1>} *

2V = 7827 calibration factor V2…………..……..…………… {Parameter: <Visc A xxx V2>} *

Q = Quality factor (no units)…………………..…..………... {Parameter: <”Q factor visc A”>}

* The Flow Computer automatically uses values for V0, V1 and V2 from a selected calibrated range.


7951 2510 (Ch11/DD) Page 11.55

11.26 VISCOSITY REFERRAL

Measurements Supported: Kinematic viscosity of fluid at base conditions. Kinematic viscosity of measured fluid at the metering point.

Figure 11.19: Viscosity Referral Blocks and Parameters

Menu Navigation List:(1) <“Configure”>/<“Viscosity”>/<”Referred viscosity”> and <”Base kin viscosity”>, (2) <“Viscosity”>/<”Header viscosity”> (3) <”Temperature”> and (4) <“Configure”>/<“Density”>/<”Meter run density”>


Index Parameters Notes? Index Parameters Notes? 70 Header kin visc * A 97 4x5 curve temp T0 73 Prime visc temp * D 98 4x5 curve temp T1 74 Meter temperature * E 99 4x5 curve temp T2 75 Visc Base temp cond 100 4x5 curve temp T3 76 Absolute zero B 101 4x5 curve temp T4 77 ASTM temperature T1 102 4x5 curve1 visc @T0 78 ASTM viscosity @T1 103 4x5 curve1 visc @T1 79 ASTM temperature T2 104 4x5 curve1 visc @T2 80 ASTM viscosity @T2 105 4x5 curve1 visc @T3 81 ASTM curve1 T1 106 4x5 curve1 visc @T4 82 ASTM curve1 T2 107 4x5 curve2 visc @T0 83 ASTM curve1 visc @ T1 108 4x5 curve2 visc @T1 84 ASTM curve1 visc @ T2 109 4x5 curve2 visc @T2 85 ASTM curve2 T1 110 4x5 curve2 visc @T3 86 ASTM curve2 T2 111 4x5 curve2 visc @T4 87 ASTM curve2 visc @ T1 112 4x5 curve3 visc @T0 88 ASTM curve2 visc @ T2 113 4x5 curve3 visc @T1 89 ASTM curve3 T1 114 4x5 curve3 visc @T2 90 ASTM curve3 T2 115 4x5 curve3 visc @T3 91 ASTM curve3 visc @ T1 116 4x5 curve3 visc @T4 92 ASTM curve3 visc @ T2 117 4x5 curve4 visc @T0 93 ASTM curve4 T1 118 4x5 curve4 visc @T1 94 ASTM curve4 T2 119 4x5 curve4 visc @T2 95 ASTM curve4 visc @ T1 120 4x5 curve4 visc @T3 96 ASTM curve4 visc @ T2 121 4x5 curve4 visc @T4


Page 11.56 7951 2510 (Ch11/DD)

VISCOSITY REFERRAL CONFIGURATION


Index Parameters Notes? Index Parameters Notes? 122 Visc referral method 124 Base kinematic visc * 123 Meter dens/visc sel C 125 Meter kinematic visc *

Notes:A Value must exceed 2 cSt for the referral calculation to be performed correctly. Turn to page 11.52 for

information on configuring this viscosity measurement.

B This parameter value is pre-set to -273.150 ( C). [MENU(3)]

C Choose the “Calculation” option when you require a referral of Header Viscosity to metering and/or base conditions. The alternative option, “Transducer”, is for when meter kinematic viscosity is to be the same as Header viscosity. [MENU(4)]

Warning! This parameter has a direct affect on the density referrals.

D Turn to page 11.34 for full configuration information. [MENU(3)]

E Turn to page 11.35 for full configuration information. [MENU(3)]


7951 2510 (Ch11/DD) Page 11.57

11.27 BASE SEDIMENT & WATER MEASUREMENTS

Measurements Supported: (As used in “Net Oil/Net Water Measurements”) BSW Analyser Input ‘A’ - from a mA Input BSW Analyser Input ‘B’ - from a mA Input Header BSW Analyser Input

Figure 11.20: BS&W Blocks and Parameters

Menu Navigation List:(1) <“Configure”>/<“Sediment & Water”>/<”Header BSW”>/<”Head BSW analyser”> (2) <“Sediment & Water”>/<”Header BSW”>/ <”Head BSW analyser”>


Index Parameters Notes? Index Parameters Notes? 1 BSW A input chl A 9 Header BSW comp limit D 2 BSW A pcent @ 100% 10 Header BSW select B 3 BSW A pcent @ 0% 11 Header BSW HI limit C 4 BSW A value * 12 Header BSW LO limit C 5 BSW B input chl A 13 BSW FB type 6 BSW B pcent @ 100% 14 BSW FB value 7 BSW B pcent @ 0% 15 Header BSW analyser *8 BSW B value * 16 Header BSW selected MENU(2)

Notes: A Ensure that the basic configuration information of the live mA input channel has been completed. (Page 11.6.)

B Nominate a logic decision table to be used by the Flow Computer whenever performing a prime measurement selection. (Also, see page 11.60)

C Optional HI and LO alarm limits. Programming the limits with a zero value will avoid maximum and minimum alarm limit checks on the associated measurement.

D Optional alarm limit. Programme it with a zero value to avoid a comparison of the two BSW measurement channels.


Page 11.58 7951 2510 (Ch11/DD)

BASE SEDIMENT & WATER MEASUREMENTS CONFIGURATION

PRIME SELECTION PROCEDURE In the event of a BSW measurement channel (‘A’ or ‘B’) failing or returning to a live state, the Flow Computer immediately attempts to select an alternative measurement channel for the prime value. The selection procedure simply involves evaluating a user-nominated logic decision table, resulting in a new prime selection.

Table 11.15: "Auto BSW A" Option Logic Table for Prime BSW

A#B (Comp)Out of Limit

BSW ‘A’ Input Failed

BSW ‘B’ Input Failed

Prime Selection

No No No A No No Yes ANo Yes No B No Yes Yes FB

Yes No No A Yes No Yes AYes Yes No B Yes Yes Yes FB

Table 11.16: "Auto BSW B" Option Logic Table for Prime BSW




Prime Selection

No No No B No No Yes ANo Yes No B No Yes Yes FB

Yes No No B Yes No Yes AYes Yes No B Yes Yes Yes FB

Table 11.17: "BSW A" Option Logic Table for Prime BSW




Prime Selection

No No No A No No Yes ANo Yes No FB No Yes Yes FB

Yes No No A Yes No Yes AYes Yes No FB Yes Yes Yes FB

Table 11.18: "BSW B" Option Logic Table for Prime BSW




Prime Selection

No No No B No No Yes FBNo Yes No B No Yes Yes FB

Yes No No B Yes No Yes FBYes Yes No B Yes Yes Yes FB


7951 2510 (Ch11/DD) Page 11.59

11.28 NET Oil/NET Water MEASUREMENTSOil/Water Mix Calculations: The “BSW Input Present” Method (Turn to pages 11.61 and 11.63 for other options)

OPTION ONE is suitable when: (a) There is a mA type field transmitter providing percentage of ‘water’ (Base Sediment and Water) values, (b) The density of the ‘water’ at base conditions is calculated by the Flow Computer, (c) The density of the oil at base conditions is a known fixed value, and (d) The density of the mixture is measured.

Prime (Indicated) Measurements: % of oil by volume (calculated) % of ‘water’ by volume (Live or fixed value) Density of oil and density of water (calculated) % of oil by mass (calculated) % of ‘water’ by mass (calculated)

Base Measurements: Density of oil at base conditions (fixed value) Density of water at base conditions (calculated)

Figure 11.21: Net Oil/ Water Calculations (“BSW Input Present” option)

Menu Navigation List:(1) <“Configure”>/<“Sediment & Water”>, (2) <“Configure”>/<“Density”>/<”Net oil/water dens”> (3) <”Configure”>/<”Base density”>, (4) <“Configure”>/<“Flow rate”>/<”Net oil/water rate”> and (5) <“Temperature”>


Index Parameter (as displayed) Notes? Index Parameter (as displayed) Notes? - Perform net calcs A 12 Base den water (net) * E- Net calcs type B 13 Line density water * E1 Header BSW analyser * E, J 14 Mass water% * E2 Header volume oil% MENU(1) 15 Mass oil% * 3 Header BSW% 16 BSW mass% LO limit H 4 Base density oil I 17 BSW mass% HI limit H 5 Dens calc sel C 18 Meter BSW% * E6 Prime density oil * 19 Meter volume oil% 7 Line density oil * 20 Meter BSW LO limit H 8 Header density * D 21 Meter BSW HI limit H 9 Prime density water * E 22 Std volume oil%

10 Water dens const A 23 Std volume water% *11 Water dens const B 24 BSW std vol% LO lmt H

See next page for continued parameter list and applicable notes.

Metering (Line) Measurements: Base Sediment and Water percentage (calculated) % of oil by gross volume (calculated) % of water by gross volume (calculated) % of oil by standard volume (calculated) % of water by standard volume (calculated) Density of oil at metering conditions (calculated) Density of water at metering conditions (calculated)


Page 11.60 7951 2510 (Ch11/DD)

NET OIL/NET WATER MEASUREMENTS OPTION ONE


Index Parameters Notes? Index Parameters Notes? 25 BSW std vol% HI lmt H 27 Meter temperature * G26 Prime dens temp * F 28 Dens Base temp cond

Notes: A By default, net flow calculations are not enabled. [MENU(4)]

B Ensure that the “Water dens calc” multiple-choice option descriptor is selected. [MENU(4)]

C Changing the selection of the referral method will also directly affect the configuration for the Meter Density and Base Density referral calculations. [MENU(3)]

D Refer to “Header Density” reference pages for details of configuring to get live values. (Page 11.38)

E The Flow Computer does not differentiate between pure water, a water based solution or water with an impurity.

F Refer to the “Density Temperature“ reference pages for details of this measurement. (Page 11.33)

G Refer to the “Meter Temperature“ reference pages for details of this measurement. (Page 11.35)

H Optional HI and LO alarm limits. Programming the limits with a zero value will avoid maximum and minimum alarm limit checks on the associated measurement

I A fixed value must be programmed (SET) into the Flow Computer. [MENU(2)]

J Refer to Section 11.27 reference pages for details of configuring this live measurement.


7951 2510 (Ch11/DD) Page 11.61

OPTION TWO NET OIL/NET WATER MEASUREMENTS

Oil/Water Mix Calculations: The “BSW Calculated” Method (Turn to pages 11.59 and 11.63 for other options)

OPTION TWO is suitable when: (a) The percentage of ‘water’ (Base Sediment and Water) is not provided by a mA transmitter but is calculated, (b) The density of the ‘water’ at base conditions is a known fixed value, (c) The density of the oil at metering-run conditions is a known fixed value, and (d) The density of the mixture is measured.

Prime (Indicated) Measurements: % of ‘water’ by volume (calculated) % of oil by volume (calculated) Density of the oil (calculated) Density of the water (calculated) % of oil by mass (calculated) % of water by mass (fixed value)

Base Measurements: Density of oil at base conditions (fixed value) and Density of water at base conditions (fixed value)

Figure 11.22: Net Oil/Water Calculations (“BSW Calculated” option)

Menu Navigation List:(1) <“Configure”>/<“Sediment & Water”>, (2) <“Configure”>/<“Density”>/<”Net oil/water dens”>, (3) <”Configure”>/<”Base density”>, (4) <“Configure”>/<“Flow rate”>/<”Net oil/water rate”> and (5) <“Temperature”>


Index Parameters Notes? Index Parameters Notes? - Perform net calcs A 9 Prime density water * F - Net calcs type B 10 Header volume oil% 1 Base density oil C 11 Header BSW% F 2 Dens calc sel D 12 Prime BSW LO limit I3 Line density oil * 13 Prime BSW HI limit I4 Prime density oil * 14 Line density water * F 5 Header density* E 15 Mass oil% 6 Base den water (net) * C, F 16 Mass water% 7 Water dens const A 17 BSW mass% LO limit I8 Water dens const B 18 BSW mass% HI limit I

See next page for continued parameter list and associated notes.

Metering (Line) Measurements: Base Sediment and Water percentage (calculated) % of oil by gross volume (calculated) % of water by gross volume (fixed or calculated) % of oil by standard volume (calculated) % of water by standard volume (fixed/ or calculated) Density of oil at line conditions (fixed or calculated)


Page 11.62 7951 2510 (Ch11/DD)

NET OIL/NET WATER MEASUREMENTS OPTION TWO


Index Parameters Notes? Index Parameters Notes? 19 Meter BSW% F 25 BSW std vol% LO lmt I20 Meter volume oil% 26 BSW std vol% HI lmt I21 Meter BSW LO limit I 27 Prime dens temp * G 22 Meter BSW HI limit I 28 Meter temperature * H23 Std volume water% F 29 Dens Base temp cond 24 Std volume oil%

Notes:A By default, net flow calculations are not enabled. [MENU(4)]

B Ensure that the “BSW calculated” multiple-choice option descriptor is selected. [MENU(4)]

C A fixed value must be programmed into the 7951.

D Changing the selection of the referral method will also directly affect the configuration for the Meter Density and Base Density referral calculations. [MENU(3)]

E Refer to “Header Density” reference pages for details of configuring to get live values. (Page 11.38)

F The Flow Computer does not differentiate between pure water, a water based solution or water with an impurity.

G Refer to the “Density Temperature“ reference pages for details of this measurement. (Page 11.33)

H Refer to the “Meter Temperature“ reference pages for details of this measurement. (Page 11.35)

I Optional HI and LO alarm limits. Programming the limits with a zero value will avoid maximum and minimum alarm limit checks on the associated measurement.


7951 2510 (Ch11/DD) Page 11.63

OPTION THREE NET OIL/NET WATER MEASUREMENTS

Oil/Water Mix Calculations: “Missing Oil Base Density” option (Turn to pages 11.57 and 11.61 for other options)

OPTION THREE is suitable when: (a) There is a mA type field transmitter providing percentage of ‘water’ (Base Sediment and Water) values, (b) The density of the oil at base conditions is calculated by the Flow Computer, (c) The density of the ‘water’ at base conditions is a known fixed value, and (d) The density of the oil/water mix is measured.

Prime (Indicated) Measurements: % of oil by volume (calculated) % of ‘water’ by volume (Live or fixed value) Density of oil and density of water (calculated) % of oil by mass (calculated) % of ‘water’ by mass (calculated)

Base Measurements: Density of oil at base conditions (calculated) Density of water at base conditions (fixed value)

Menu Navigation List:(1) <“Configure”>/<“Sediment & Water”>, (2) <“Configure”>/<“Density”>/<”Net oil/water dens”>, (3) <”Configure”>/<”Base density”>, (4) <“Configure”>/<“Flow rate”>/<”Net oil/water rate”> and (5) <“Temperature”>


Index Parameters Notes? Index Parameters Notes? - Perform net calcs A 12 Base den water (net) * I ,E - Net calcs type B 13 Line density water * E1 Header BSW analyser * E, J 14 Mass water% * E2 Header volume oil% 15 Mass oil% *3 Header BSW% 16 BSW mass% LO limit H 4 Base density oil 17 BSW mass% HI limit H 5 Dens calc sel C 18 Meter BSW% * E6 Prime density oil * 19 Meter volume oil% 7 Line density oil * 20 Meter BSW LO limit H 8 Header density* D 21 Meter BSW HI limit H 9 Prime density water * E 22 Std volume oil%

10 Water dens const A 23 Std volume water% *11 Water dens const B 24 BSW std vol% LO lmt H

See next page for continued parameter list and associated notes.

Metering (Line) Measurements: % of oil by gross volume (calculated) % of ‘water’ by gross volume (calculated) % of oil by standard volume (calculated) % of water by standard volume (calculated) Density of oil at metering conditions (calculated) Density of water at metering conditions (calculated)


Page 11.64 7951 2510 (Ch11/DD)

NET OIL/NET WATER MEASUREMENTS OPTION THREE


Index Parameters Notes? Index Parameters Notes? 25 BSW std vol% HI lmt H 27 Meter temperature * G26 Prime dens temp * F 28 Dens Base temp cond

Notes: A By default, net flow calculations are not enabled. [MENU(4)]

B Ensure that the “Oil dens calc” multiple-choice option (descriptor) is selected. [MENU(4)]

C Changing the selection of the referral method will also directly affect the configuration for the Meter Density and Base Density referral calculations. [MENU(3)]

D Refer to “Header Density” reference pages for details of configuring to get live values. (Page 11.38)

E The Flow Computer does not differentiate between pure water, a water based solution or water with an impurity

F Refer to the “Density Temperature“ reference pages for details of this measurement. (Page 11.33)

G Refer to the “Meter Temperature“ reference pages for details of this measurement. (Page 11.35)

H Optional HI and LO alarm limits. Programming the limits with a zero value will avoid maximum and minimum alarm limit checks on the associated measurement

I A fixed value must be programmed into the Flow Computer

J Refer to Section 11.27 reference pages for details of configuring this live measurement. (See page 11.57)


7951 2510 (Ch11/DD) Page 11.65

11.29 NET OIL /NET ‘WATER’ FLOW RATES AND TOTALS

Measurements Supported: Net ‘Water’ Volume flow rate and totals Net ‘Water’ Standard Volume flow rate and totals Net ‘Water’ Mass flow rate and totals Net Oil Volume flow rate and totals Net Oil Standard Volume flow rate and totals Net Oil Mass flow rate and totals

Note: Ensure that Net Oil/Net Water Measurements, Flow Rates and Flow Totals are already configured.

Figure 11.23: Net ‘Water’ Flow Rates and Metering-run Totals

Figure 11.24: Net Oil Flow Rates and Metering-run Totals


Page 11.66 7951 2510 (Ch11/DD)

NET OIL /NET ‘WATER’ FLOW RATES AND TOTALS

Menu Navigation List:(1) <“Configure”>/<“Flow rate”>/<”Net oil/water rate”>, (2) <“Configure”>/<“Totalisation”>/<”Standard”>, (3) <“Health check”>/<”Totals”>, (4) <“Flow totals”>/<”Net oil & Water”>, and (5) <”Sediment & water”>


Index Parameters Notes? Index Parameters Notes? 1 Meter BSW% * 30 Oil vol HI limit E 2 Gross volume rate * 31 Oil vol LO limit E 3 Water vol rate * 32 Oil volume roll C 4 Water volume roll C 33 Oil vol inhibit 5 Water volume inhibit 34 Oil volume inc B 6 Water volume inc B 35 Oil volume total A 7 Water volume total A 36 Maint NV oil inc B 8 Maint NV water inc B 37 Maint NV oil total A 9 Maint NV water total A 38 Line density oil * 10 Line density water * 39 Base density oil * 11 Base den water (net) * 40 Oil std vol rate * 12 Water std vol rate * 41 Oil std vol HI limit E 13 Water std vol roll C 42 Oil std vol LO limit E 14 Water std vol inhib 43 Oil std vol roll C 15 Water std vol inc B 44 Oil std vol inhibit 16 Water std vol total A 45 Oil std vol inc B 17 Maint NSV water inc B 46 Oil std vol total A 18 Maint NSV water totl A 47 Maint NSV oil inc B 19 Water mass rate * 48 Maint NSV oil total A 20 Water mass roll C 49 Oil mass rate * 21 Water mass inhibit 50 Oil mass HI limit E 22 Water mass inc B 51 Oil mass LO limit E 23 Water mass total A 52 Oil mass roll C 24 Maint NM water inc B 53 Oil mass inhibit 25 Maint NM water total A 54 Oil mass inc B 26 Operating mode D 55 Oil mass total A 27 Rate flowstop action 56 Maint NM oil inc B 28 Meter volume oil% 57 Maint NM oil total A 29 Oil vol rate * - Flow status D

Notes:A A total is the integration of a specific parameter value (e.g. metering-run flow rate) over a period of time. The

Flow Computer updates a total with an increment value every cycle - See Note B. [MENU(4)]

B An increment value is calculated by integrating a parameter value, e.g. flow rate, over time. The result is added to a corresponding total once during every machine cycle. [MENU(3)]

(a) Orifice or Coriolis Flow The time element of the increment calculation is the ‘actual cycle time’. This value is the elapsed time between a flow measurement. It is available for viewing from within the <“Time”> menu.

(b) Turbine Flow The time element of the increment calculation is the ‘pulse sample time’ – the period that pulses were accumulated for calculating the present value of the Indicated Volume flow rate. This time value is available for viewing within the <”Health check”> feature menu.

Editing an increment value has no effect.

C By default, rollover (to zero) limits are SET to a very large number. However, it is advisable to check that the limit is sufficient for the metering application. [MENU(2)]


7951 2510 (Ch11/DD) Page 11.67

NET OIL/NET ‘WATER’ FLOW RATES AND TOTALS

D There are two Flow Computer modes to be aware of:

1. Normal modeIn this mode, a main total, e.g. <”Water volume total”>, can increment. The twinned maintenance-mode total, e.g. <”Maint NV water total”>, will never increment.

2. Maintenance modeIn this mode, a maintenance-mode total, e.g. <”Maint NV water total”>, can increment. The twinned normal-mode total, e.g. <”Water volume total”>, will never increment.

A mode can be selected only when the Flow Computer is in a ‘Flow Stopped’ state. See flow metering reference pages for parameters involved in establishing a ‘Flow stopped’ state.

[INFORMATION (BUTTON) MENU]

E Optional HI and LO alarm limits. Programming the limits with a zero value will avoid maximum and minimum alarm limit checks on the associated measurement. [MENU(1)]


Page 11.68 7951 2510 (Ch11/DD)

NET OIL/NET ‘WATER’ MEASUREMENTS EQUATION LIST

Net oil and water equations: (Note: Listed equations do not conform to a Standard unless otherwise stated)

Equation NC#1: Net Oil Volume Flow Rate

Using: OilNV =100%Oil*Q Line

GV

Where: OilNV = Net Oil Volume flow rate…………………….……..………. {Parameter: <”Oil vol rate”>}

GVQ = Gross Volume flow rate……………………….………….… {Parameter: <”Gross volume rate”>}

Line%Oil = Percentage of oil at the metering point ………….……..... {See Equation )……………………………...… NC#7b}

Equation NC#2: Net ‘Water’ Volume Flow Rate

Using: WaterNV =100

%Water*Q LineGV

Where: WaterNV = Net Oil Volume flow rate………………………..……... {Parameter: <”Water vol rate”>} GVQ = Gross Volume flow rate……………………….…….…. {Parameter: <”Gross volume rate”>}

Line%Water = Percentage of water in mix at the metering point….... {See Equation NC#8c}

Equation NC#3: Net Oil Standard Volume Flow Rate

Using: OilNSV = BaseOil

LineOil

Oil *NV

Where: OilNSV = Net Oil Standard Volume flow rate………..…..………….. {Parameter: <”Oil std vol rate”>}

OilNV = Net Oil Volume flow rate………..……....…………...…….. {See Equation NC#1 on page 11.68} LineOil = Density of the oil at the metering point….……......……… {Parameter: <”Line density oil”>}

BaseOil = Density of the oil at base conditions……………. ……..... {Parameter: <”Base density oil”>}

Equation NC#4: Net ‘Water’ Standard Volume Flow Rate

Using: WaterNSV =BaseWater

LineWater

Water *NV

Where: WaterNSV = Net ‘Water’ Standard Volume flow rate….…..…..………. {Parameter: <”Water std vol rate”>}

WaterNV = Net ‘Water’ Volume flow rate………..……..……...…….... {See Equation NC#2 on page 11.68} LineWater = Density of the ‘water’ at the metering point……....……… {See Equation NC#9c on page 11.71}

BaseWater = Density of the ‘water’ at base conditions …………..…..... {See Equation NC#9d on page 11.71}

Equation NC#5: Net oil Mass Flow Rate

Using: OilNM = LineOilOil *NV

Where: OilNM = Net oil mass flow rate……………….…………………………… {Parameter: <”Oil mass rate”>}

OilNV = Net Oil Volume flow rate…………….………………………….. {See Equation NC#1 on page 11.68} LineOil = Density of the oil at the metering point…..…….……………… {Parameter: <”Line density oil”>}


7951 2510 (Ch11/DD) Page 11.69

EQUATION LIST NET OIL/NET ‘WATER’ MEASUREMENTS

Equation NC#6: Net Water Mass Flow Rate At the metering point:

Using: WaterNM = LineWaterWater *NV

Where: WaterNM = Net water mass flow rate……….……………………..…… {Parameter: <”Water mass rate”>}

WaterNV = Net ‘water’ volume flow rate…..…………………….…….. {See Equation NC#2 on page 68} LineWater = Density of the ‘water’ at the metering point…..…..……… {See Equation NC#9c on page 11.71}

Equation NC#7: Percentage of oil by volume Prime Input:

Using: Prime%Oil = (100 - Head%Water )………………………..….… NC#7a

Where: Prime%Oil = Indicated percentage of oil in mix…….………….…. {Parameter: <”Header volume oil%”>}

Prime%Water = Indicated percentage of ‘water’ in mix,………….….. {See Equation NC#8 on page 11.69}

At the metering point: Using: Line%Oil = (100 - Line%Water )……………………………...… NC#7b

Where: Line%Oil = Percentage of oil in mix at the metering point….….… {Parameter: <”Meter volume oil%”>}

Line%Water = Percentage of ‘water’ in mix at the metering point….. {See Equation NC#8c on page 11.70}

Equation NC#8: Percentage of ‘water’ by volume

Note: This measurement is also known as BSW - ‘Base Sediment and Water’.

Prime Input: Equation NC#8a is applicable when either the “Water dens calc” option or the “Oil dens calc” option is selected.

Using: Prime%Water = MinRawMinMax %BSW%BSW*

100%BSW%BSW ...NC#8a

Where: Prime%Water = Indicated percentage of ‘water’ in mix.…….……….. {Parameter: <”Header BSW%”>}

Raw%BSW = Reading from transmitter……………...…………….. {Parameter: <”BS&W value”>}

Max%BSW = Maximum percentage from transmitter…………….. {Parameter: <”BS&W pcent @ 100%”>}

Min%BSW = Minimum percentage from transmitter…...………… {Parameter: <”BS&W pcent @ 0%”>}

Equation NC#8b is applicable when the “BSW Calculated” option is selected.

Using: Prime%Water = 100*PrimeOil

PrimeWater

PrimeOil

PrimeMix …………………………..NC#8b

Where: Prime%Water = Indicated percentage of ‘water’ flowing…………….. {Parameter: <”Header BSW%”>}

PrimeMix = Indicated density of the oil/water mixture……..……. {Parameter: <”Prime txdr density”>} **

PrimeOil = Indicated density of the oil………...…………………. {Parameter: <”Prime density oil”>} *

HeadWater = Indicated density of the ‘water’……...……….…….... {See Equation NC#9 on page 11.70}

* This is a SET (fixed) value when using the “BSW Calculated” option. For other options, see Equation NC#16 on page 11.72. ** Refer to “Density” reference pages for information on configuring this parameter.


Page 11.70 7951 2510 (Ch11/DD)


Net oil and water equations continued… (Listed equations do not conform to a Standard unless otherwise stated)

(Equation NC#8 continued…)

Note: This measurement is also known as ‘Base Sediment and Water’.

At the metering point:

Using: Line%Water = 100*LineOil

LineWater

LineOil

PrimeMix …………..………..…….….. NC#8c

Where: Line%Water = Percentage of ‘water’ flowing at the metering point ... {Parameter: <”Meter BSW%”>}

LineOil = Density of the oil at the metering point ……….……… {Parameter: <”Line density oil”>}

LineWater = Density of the ‘water’ at the metering point ……….…. {See Equation NC#9c on page 11.71}

And: PrimeMix =

LineWaterOil

LineOilOil

LineOil

LineWater

LineOil

*%Mass*%Mass*100

**100

Where: LineOil = Density of the oil at the metering point.……..….….…. {Parameter: <”Line density oil”>}

LineWater = Density of the ‘water’ at the metering point…..………. {Parameter: <”Line density water”>}

Oil%Mass = Percentage of oil (by mass) at the metering point ..… {See Equation NC#11 on page 11.71}

Equation NC#9: Water Density

Prime Input:

Equation NC#9a is applicable when either the “Water dens calc” option or the “Oil dens calc” option is selected.

Using: PrimeWater = Prime

OilHead

PrimeOil

PrimeMix

%Water

*100…………………….……NC#9a

Where: PrimeWater = Indicated density of the ‘water’…………..…………….….……..{Parameter: <”Prime density water”>}

PrimeMix = Indicated density of the oil/water mixture…………….….………{Parameter: <”Prime txdr density”>}

PrimeOil = Indicated density of the oil……………………………………….. {See Equation NC#16 on page 11.72}

Equation NC#9b is applicable when the “BSW Calculated” option is selected.

Using: PrimeWater = t*t*Bt*ABase

Water …………...……………………. NC#9b

Where: PrimeWater = Indicated density of the ‘water’…………..………………..…….{Parameter: <”Prime density water”>}

BaseWater = Density of the ‘water’ at base conditions…………………….… {See Equation NC#9d on page 11.71}

A = Water density constant ‘A’………………………..………..…….. {Parameter: <”Water dens const A”>}

B = Water density constant ‘B’………………………..………..…….. {Parameter: <”Water dens const B”>}

And: t = basePrime tt

Where: Primet = Temperature of the oil/water mixture at the ‘density loop’…{Parameter: <”Prime dens temp”>}

Baset = Temperature of the oil/water mixture at base conditions.... {Parameter: <”Dens Base temp cond”>}


7951 2510 (Ch11/DD) Page 11.71

EQUATION LIST NET OIL/NET ‘WATER’ MEASUREMENTS

Net oil and water equations continued… (Listed equations do not conform to a Standard unless otherwise stated)

(Equation NC#9 ‘Water’ Density continued…)

At the metering point:

Using: LineWater = t*t*Bt*ABase

Water …………………..………...…NC#9c

Where: LineWater = Density of the ‘water’ at the metering point…..…………….{Parameter: <”Line density water”>}

BaseWater = Density of the ‘water’ at base conditions……………...…… {See Equation NC#9d on page 11.71}

A = ‘Water’ density constant ‘A’…………………..….………….. {Parameter: <”Water dens const A”>}

B = ‘Water’ density constant ‘B’……………………...………….. {Parameter: <”Water dens const B”>}

And: t = baseLine tt

Where: Linet = Temperature of the oil/water mixture at a Metering-Run…. {Parameter: <”Meter temperature”>}

Baset = Base temperature…………………………………………….. {Parameter: <”Dens Base temp cond”>}

At base conditions:

EquationNC#9d is applicable when the “Water dens calc” option is selected. (Density of the ‘water’ at base conditions must be a SET (fixed) value if not using the “Water dens calc” option)

Using: BaseWater = t*t*Bt*APrime

Water ………………………..……NC#9d

Where: BaseWater = Density of the ‘water’ at base conditions..………………….{Parameter: <”Base den water (net)”>}

PrimeWater = Indicated density of the ‘water’.………………………..…… {See Equation NC#9a or NC#9b}

A = ‘Water’ density constant ‘A’…………………….……………. {Parameter: <”Water dens const A”>}

B = ‘Water’ density constant ‘B’…………………….……………. {Parameter: <”Water dens const B”>}

And: t = basePrime tt

Where: Primet = Prime temperature of the oil/water mixture………..………. {Parameter: <”Prime dens temp”>}

Baset = Base temperature…………………………………………….. {Parameter: <”Dens Base temp cond”>}

Equation NC#10: Percentage of mass (‘water’)

Using: Water%Mass =

100**

*PrimeOil

PrimeWater

LineMix

PrimeOil

PrimeMix

PrimeWater

Where: Water%Mass = Percentage of ‘water’ (by mass) flowing…………. {Parameter: <”Mass water%”>}

PrimeWater = Indicated density of the ‘water’…………….……… {See Equation NC#9a or NC#9b}

PrimeMix = Indicated density of the oil/water mixture….…….. {Parameter: <”Prime txdr density”>}

PrimeOil = Density of the oil mixture at the Header…..……… {Parameter: <”Prime density oil”>}

Equation NC#11: Percentage of mass (‘oil’)

Using: Oil%Mass = Water%Mass100

Where: Oil%Mass = Percentage of mass for oil flowing in system..……{Parameter: <”Mass oil%”>}

Water%Mass = Percentage of mass for ‘water’ flowing…………… {See Equation NC#10 on page 11.71}


Page 11.72 7951 2510 (Ch11/DD)


Equation NC#12: Percentage of standard volume (‘water’)

Using: Water%StdVol =

Water

BaseWater

BaseOil

Oil%Mass

*%Mass1

100

Where: Water%StdVol = Percentage of the ‘water’ (by Standard Volume).. {Parameter: <”Std volume water%”>}

Oil%Mass = Percentage of the oil (by Mass)…………………… {See Equation NC#11 on page 11.71}

Water%Mass = Percentage of the ‘water’ (by Mass).…………….. {See Equation NC#10 on page 11.71}

BaseOil = Density of the oil at base conditions…………....... {Parameter: <”Base density oil”>}

BaseWater = Density of the ‘water’ at base conditions …………{See Equation NC#9d}

Equation NC#13: Percentage of standard volume (oil)

Using: Oil%StdVol = Water%StdVol100

Where: Oil%StdVol = Percentage of the oil (by Standard Volume)……. {Parameter: <”Std volume oil%”>}

Water%StdVol = Percentage of the ‘water’ (by Standard Volume).. {See Equation NC#12 on page 11.72}

Equation NC#14: Specific gravity for the oil

Using: OilSG =BaseWater

BaseOil

Where: OilSG = Specific gravity for the oil………………………….. {Parameter: <”Oil specific gravity”>}

BaseOil = Density of the oil at base conditions…………....... {Parameter: <”Base density oil”>}

BaseWater = Density of the ‘water’ at base conditions ………… {See Equation NC#9d on page 11.71}

Equation NC#15: Degrees API (oil)

Using: OilAPI = 5.131SG

5.141Oil

Where: OilAPI = Degrees API for the oil………………………………{Parameter: <”Oil degrees API”>}

OilSG = Specific gravity for the oil……………………...…… {See Equation NC#14 }

Equation NC#16: Oil Density Calculation (prime) This calculation is applicable when the “Oil dens calc” option is selected. All other options use a SET (fixed) value for the indication density of the oil (in a mixture).

Using: PrimeOil = Prime

Water

PrimeWater

PrimeMix

%BSW100

100*

Where: PrimeOil = Indicated oil density……………..…………..……….{Parameter: <”Prime density oil ”>}

PrimeMix = Indicated density of the oil/water mixture………….{Parameter: <”Prime txdr density”>} *

PrimeWater = Indicated density of the ‘water’…………….……… {See Equation NC#9a}

Prime%Water = Indicated percentage of ‘water’ in mix.…….…...... {Parameter: <”Header BSW%”>}

* Refer to “Density” reference pages for information on configuring this parameter.


7951 2510 (Ch11/DD) Page 11.73

11.30 LIVE ANALOG OUTPUTS

Feature:Analog Outputs supported by the 7951:mA output channels 1 to 4 (without extra I/O option) or mA output channels 1 to 8 (with extra I/O option)

What to do: Use this reference page to find out how to configure the analogue output channels that are to transmit values to external devices once every machine cycle. By default, no parameters are pre-allocated to the analogue outputs. After configuring, check that a satisfactory live reading is displayed by the <mA output value> Parameter page.

Menu Navigation List:(1) <“Configure”>/<”Outputs”>/<“mA outputs”> and (2) <“Health check”>/ <”Outputs”>/<“mA outputs”>


Analog Channel (and signal types)

Parameters Analog Channel (and signal types)

Parameters

mA output 1 value * mA output 5 value *mA output 1 ptr list mA output 5 ptr list mA 1 param val @100% mA 5 param val @100% mA 1 param val @0% mA 5 param val @@ 0% mA output 1 type mA output 5 type mA output 1 filter mA output 5 filter

Analog Output 1 (mA only)

mA output 1 source

Analog Output 5 **(mA only)

mA output 5 source mA output 2 value * mA output 6 value *mA output 2 ptr list mA output 6 ptr list mA 2 param val @100% mA 6 param val @100% mA 2 param val @0% mA 6 param val @0% mA output 2 type mA output 6 type mA output 2 filter mA output 6 filter


mA output 2 source




mA output 3 source




mA output 4 source


mA output 8 source

Note:

** Requires option card to be fitted and <”Available channels”> parameter edited to show a value of “8”.

A The <mA output source> parameter is for selecting a parameter that is not readily available with the normal <mA output ptr list> parameter. It is necessary to select the “USER” option descriptor for <mA output ptr list> and then program <mA output source> with the parameter’s unique identification number.


Page 11.74 7951 2510 (Ch11/DD)

11.31 INTERFACE DETECTION

Features: Product Detection (using measurement zoning – Meter run density, Base density, SG, Header mA density or API)Product Totals (Gross Volume, Gross Standard Volume and Mass totals for up to 20 products)

Figure 11.25: Interface Detection Blocks and Parameters

Menu Navigation List: (1) <“Configure”>/<“Product Detect”>, (2) <“Density”>, (3) <“Flow rates”>, (4) <“Flow totals”>/<“Product totals”>

Parameter List: * shows data that can be “Live” or “Set” Index Parameters Notes? Index Parameters Notes?

1 Meter run density * 17 Prod1 dens Txdr FB A, E 2 Base density * 18 Product time delay C 3 SG Value * 19 Current Product ID *4 Head analog dens * B 20 Product totalisation D 5 Degrees API * 21 Gross vol rate *6 Product zone type I 22 Product 1 GV total D 7 Band hysteresis 23 Gross std vol rate *8 Product 1 name A 24 Product 1 GSV total D 9 Product 1 Band HI A 25 Mass rate *10 Product 1 Band LO A 26 Product 1 Mass total D 11 Prod1 MF A, E, F 27 Non-Band product ID G 12 Prod1 K factor A, E, F 28 Product auto config H 13 Prod1 dens calc sel A, E 29 Reset totalisers 14 Prod1 API product A, E 30 Meter curve type (E) 15 Prod1 API range A, E 16 Prod1 Prime dens FB A, E

Notes:A A maximum of 20 product profiles can be defined. To illustrate, the parameters 8 - 17 are the profile for

product one. Profiles of other products are not shown in the schematic or list for reasons of clarity. Each product profile has a corresponding set of product totals – see Parameter items 22, 24 and 26.

B This is for fluid density measurements from a mA-type field transmitter at the header. Values are used as advanced notification of a product change. (Also, see note ‘C’ and configuration details on page 11.38)

C This is a programmable period for allowing a product change at header instrumentation to reach the metering point. Product switching should not occur until the fluid reaches the metering point. (Also, see note ‘B’)

D Product totalising can be switched on and off with this parameter. If switched off, increments for product totals are discarded. If switched on, the Flow Computer will calculate increments and then update the appropriate set of product totals.


7951 2510 (Ch11/DD) Page 11.75

CONFIGURATION INTERFACE DETECTION

E This data is a part of the Automatic Product Configuration feature. The programmed (SET) value can be copied to the relevant prime parameter whenever the product is detected.

For example, the value for <“Prod1 MF”> would overwrite the value of the <“Meter factor”> parameter as soon as Product #1 is detected, but only if the ‘Meter Factor’ is not being linearised.

Similarly, the value for <“Prod1 K factor”> would overwrite the value of the <“Flowmeter K Factor”>parameter as soon as Product #1 is detected, but only if the ‘K-factor’ is not being linearised.

(N.B. See earlier flow metering pages for use of <“Meter Factor”> and <“Flowmeter K Factor”>)

F Retrospective total calculations can be performed to compensate for changes to the ‘Meter Factor’ or the ‘K-factor’. Specify the volume to be considered when correcting totals.

G One set of product totals can be allocated to all fluids that are outside the defined product bands. High and low band data in the selected product profile are not applied.

H Enables or prevents the overwriting of parameters with ‘override’ values from the profile of a detected product. (Also, see note ‘E’)

I Selecting a new zone type will automatically re-select the appropriate base units of measurement for data listed in all 20 product profiles.

Example: Density zoning with 4 defined products (i.e. 4 back-to-back bands)

Parameters Reference in Picture

Product 1 Band High DF

Product 1 Band Low DE

Product 2 Band High DE

Product 2 Band Low DD

Product 3 Band High DD

Product 3 Band Low DC

Product 4 Band High DA

Product 4 Band Low D0

Product 1 totals increment between time T1 and T2.

Product 2 totals increment between time T2 and T3. Product 3 totals increment between time T3 and T4. Product 4 totals do not increment. “Non-product” totals increment between times T0 to T1 and T4 to TN.


Page 11.76 7951 2510 (Ch11/DD)

INTERFACE DETECTION CONFIGURATION

Example: Using Hysteresis

Hysteresis overcomes the difficulties when product bands overlap.

Parameters FigureRef.

SETValue

Hysteresis Calc. Value

Product 1 Band High DA 1000 1010.00 Product 1 Band Low DB 795 802.95 Product 2 Band High DB 795 787.05 Product 2 Band Low DC 595 600.95 Band hysteresis - 1% -

1. Hysteresis point calculations when product one is current detected product:

10011*DA A1 100

11*DB B1

999.0*1000A1 01.1*790B1

0.990A1 95.802B1

Switch (up) to product 1 from product 2 at just over 802.95 Kg/m3. Switch (up) to non-product takes place at just over 1010 Kg/m3. Switch (down) to product 1 from non-product is at exactly 1000 Kg/m3. (The 990 Kg/m3 point is ignored)

2. Hysteresis band calculations when product two is current detected product:

10011*DA B2 100

11*DB C2

99.0*795A2 01.1*595B2

05.787A2 95.600B2

Switch (down) to product 2 from product 1 at just under 787.05 Kg/m3.


7951 2510 (Ch11/DD) Page 11.77

11.32 DIGITAL OUTPUTS

Features:

Digital Outputs supported by a 7951 (D-Type) Status output channels 1 to 8 (without extra I/O option), or Status output channels 1 to 16 (with extra I/O option)

Digital Outputs supported by a 7951 (Klippon) Status output channels 1 to 6

What to do:

This reference page will assist when configuring basic data (see list below) for all the Status Output channels that are being used. Later tasks will expect this Parameter to be already configured.

By default, several Status Outputs are reserved for the Alarm Logger Output feature. (See Chapter 8) The remaining outputs are available for use as listed in Chapter 3.

In the <“Health Check”> menu there is a Status Output sub-menu. It contains a parameter with a series of digits on the 2nd display line. Each digit indicates the present state of an individual output.

Menu Navigation List: (1) <“Configure”>/<”Outputs”>/<“Status outputs”>, and (2) <“Health check”>/<”Outputs”>/<“Status outputs”>


Status O/P Channel

Parameters Status O/P Channel

Parameters Status O/P Channel

Parameters

1 Status out 1 logic 7 Status out 7 logic 13 Status out 13 logic 2 Status out 2 logic 8 Status out 8 logic 14 Status out 14 logic 3 Status out 3 logic 9 Status out 9 logic 15 Status out 15 logic 4 Status out 4 logic 10 Status out 10 logic 16 Status out 16 logic 5 Status out 5 logic 11 Status out 11 logic 6 Status out 6 logic 12 Status out 12 logic

General Note:

A Digital Outputs 1 to 3 are permanently reserved for use by the Alarm Logger Output feature seen in Chapter 8. This is why there is a permanent “XXX” seen in the first three digits of <“Status out [1-16]”>.

Digital Outputs 4 to 16 are not pre-allocated to a Flow Computer feature. They are mainly used by the support for flowmeter proving, as guided in Chapters 16A/16B.


Page 11.78 7951 2510 (Ch11/DD)

11.33 LIVE PULSE OUTPUTS

Features: Pulse Outputs supported by a 7951 (D-Type)

Pulse Output channels 1 to 5

Pulse Outputs supported by a 7951 (Klippon) Pulse Output channels 1 to 3

What to do:

Use this page to configure basic information for the pulse output channels. A channel can be set-up to transmit each increment to a normal mode total as a pulse train, suitable for an external counter.

The individual pulse has a significance that equates to a certain mass or volume in the units of measurement already selected for the rate. As an example, consider a flow total increasing at a steady rate of one gallon every second and significance that is programmed with a value of six, representing six gallons. This would result in a single pulse being transmitted every 6 seconds.

Menu Navigation List: (1) <“Configure”>/<“Outputs”>/<”Pulse outputs”>

Parameter List: ** Channel is available on a 7951 with the D-Type rear panel

Pulse Output Channel Parameters Pulse Output Channel Parameters

Pulse output 1 src Pulse output 4 src Pulse Output 1 Pulse output 1 sig

Pulse Output 4 ** Pulse output 4 sig

Pulse output 2 src Pulse output 5 src Pulse Output 2 Pulse output 2 sig

Pulse Output 5 ** Pulse output 4 sig

Pulse output 3 src Pulse Output 3 Pulse output 3 sig

General Notes:

A By default, parameters are not pre-allocated to pulse outputs.

B If the pulse frequency exceeds 10Hz (10 complete pulses per second), a ‘reservoir’ is used to keep a count of the excess. Always SET a large enough pulse significance to avoid this occurring; if there is an excess, increase the significance value and wait for things to calm down again. Alternatively, all reservoirs can be cleared immediately by selecting the “Clear” command through the <“Clear pulse outputs”> parameter.

C Pulses are transmitted at evenly calculated intervals within the ‘window’ of a machine cycle. As the actual machine cycle time always varies, the calculated interval between pulses will vary even when the value from the Pulse Output Source (e.g. a flow rate) has not changed – see Figure 11.26.

1.05 Seconds(Actual Cycle Time)

1.2 Seconds(Actual Cycle Time)

0.525s 0.6s

Figure 11.26: Examples of pulse output distribution (for two machine cycles)


7951 2510 (Ch11/DD) Page 11.79

11.34 PASSWORDS AND SECURITY

This sub-section explains how the 7951 can set-up to restrict access to facilities.

Securable and non-secure modes: The Flow Computer can work in a non-secure or securable mode. In non-secure mode, anyone can have access to any of the facilities. In securable mode, access to facilities can be protected by passwords.

Changing security mode:In the 7951 and 7955 instruments, you change the security mode by using the key switch on the front of the instrument. The instruments are normally securable but, when you insert the key and turn it clockwise, this changes the mode to non-secure. You can only withdraw the key in the vertical (securable) position.

(1) Security Lock and Security Level LED

Figure 11.27: The security lock on the 7951 instrument

Passwords and Security Levels A password system restricts access to its facilities to those people with certain levels of authority. There are four levels of Flow Computer security:

Calibration (also referred to as the “Programmer” security level)

Engineer

Operator

World (anyone other than those listed above).

The table below lists what facilities each of these groups can access.

Access levels, and what they can have access to Facilities available

Calibration Engineer Operator World

Programmable parameters except

security codes YES YES

All data or functions which don’t affect

results of calculations NO

Security codes YES NO NO NO

Programming facilities YES YES NO NO

Calibration facilities YES NO NO NO

How the security LED appears RED flashing RED ORANGE GREEN


Page 11.80 7951 2510 (Ch11/DD)

PASSWORDS AND SECURITY

Setting or changing a password (security level code)

1. Firstly, use the routine <“Enter Password”> parameter for entering the password to change to the required “Calibration” (Programmer) security level.

2. From this menu, make a selection appropriate for the password (Programmer, Engineer, Operator or World) you want to define or change, then type in a password of up to 20 characters. You can clear an existing password by pressing the CLR button. You can also have the same password for more than one security level. This would give you access to the facilities of all the levels covered by that password.

Feature: Keyboard Security Fallback (Optional)The present security level for information access through the keyboard can be automatically changed to “World” access after a user-defined period has elapsed without use of the keyboard. Use of the keyboard during that period causes the ‘lockout’ timer to be re-started. Security level changes can still be made at any time in the normal way (as explained earlier) but they will re-start the timer.

By default, this security feature is not active. To activate, the length of time for the period must be programmed (SET) to a value more than zero. Passwords to change security level are as already defined.

Configuration task: Enable keyboard security fallback Follow these instructions: 1. Navigate to this menu: <“Configure”>/<“Other parameters”>/<“Security”>/<“User interface”>

2. Locate the “Security timeout” parameter and then programme (SET) a value for the time-out period. It is not advisable to programme a time of less than 15 seconds. To de-activate this feature, programme (SET) the “Security timeout” parameter with a value of zero.

Feature: Communications Security Fallback (Optional)Virtual slave access through the serial port can be blocked after a period has elapsed without use. Writing a communications password to database location 3187 is then the only way to un-block the serial port. Using the serial communication link during the period causes the ‘lockout’ timer to be re-started.

By default, this feature is not active. To activate it, the length of time must be programmed (SET) to a value of more than zero. A communications password should be also programmed rather than keep the default one.

Configuration task: Enable communications security fallback Follow these instructions: 1. Change security level to “Calibration” (i.e. flashing red security LED).

2. Navigate to this menu: <“Configure”>/<“Other parameters”>/<“Security”>/<“Communications”>.

3. Locate the <“Comms secure timeout”> parameter, and then programme (SET) a value for the time-out.

4. (Optional) Locate the <“Comms password”> parameter, and then programme a new password.

To de-activate this feature, SET the value of the <“Comms secure timeout”> parameter to zero.


7951 2510 (Ch11/DD) Page 11.81

11.35 MULTI-VIEW

What is Multi-view?Multi-view (often referred to as the “User Display”) is a display, which you define to show whatever information you want. It consists of one or more pages with the four lines on each page comprising of either or both of:

Text (such as the name of a parameter), at the left of the line. A value for a parameter, at the right of the line.

You can change the configuration of a multi-view display whenever you wish. An example of a typical multi-view display is shown in Figure 11.28.

How to get into Multi-viewTo see the first Multi-view display page, press the MULTI-VIEW DISPLAY button. A multi-view display page looks like the example below.

Figure 11.28: A typical multi-view display page

Use the DOWN-ARROW button to page down through other multi-view displays. The message “Invalid MultiView Page” appears to indicate that no further pages are defined. Use the UP-ARROW button to reverse through the display pages.

Configuring Multi-viewFollow this procedure for configuring Multi-view:

Step 1: Decide what text you want to display

You almost certainly want each line of the Multi-view display to show the name (possibly in an abbreviated form) of a parameter whose value you want to display. Bear in mind that:

Text cannot exceed 11 characters. The display leaves a space between the text and value. The value is displayed as a number without any units. You may wish to include the units as part of the text.

Step 2: Find the database location IDs of the parameters

1. In the menu system, find the parameter you want 2. Press the ‘a’ button to display the location identification number (ID:xxxx). 3. Note down that ID number. 4. Repeat this for the other parameters.

Step 3: Open the Multi-view configuration menu 1. Navigate to this menu: <”Configure”>/<”Multi-view”>.

Text width setting – a movable boundary between text and value

Text (e.g. parameter names) Value of parameter


Page 11.82 7951 2510 (Ch11/DD)

MULTI-VIEW CONFIGURATION

Step 4: Entering the text and location ID for each line

1. Select whichever multi-view page (1 - 15) you want to configure. 2. Select whichever line (1 - 4) you want to configure. 3. Enter the line text you require. 4. Enter the parameter (database location ID) you require. Note that after the location ID is entered, the display

changes to show the name of the parameter.

Step 5: Set the text width

The text width is the number of characters you want the text to occupy. If you want to set the text width:

1. Navigate to the <Text width> parameter.

2. Edit the text width value.

Step 6: Press the MULTI-VIEW DISPLAY button

Chapter 12 Routine operation (Data maps)

7951 2510 (Ch12/BE) Page 12.1

12. Routine operation (Data Maps)

12.1 Viewing the data The diagrams on the following pages show that part of the menu structure which you use to carry out routine tasks such as checking results or changing units of measurement.

12.1.1 Data Map: Flow rates and totals…………………………………… 12.2

12.1.2 Data Map: Density, Base density and Specific Gravity….…….12.3

12.1.3 Data Map: Viscosity………………………………………….……….. 12.4

12.1.4 Data Map: Temperature and pressure……………………………. 12.5

12.1.5 Data Map: Smaller topics…………………………….…...…………. 12.6


Page 12.2 7951 2510 (Ch12/BE)

12.1.1 Data Map: Flow rates and totals

Flow rates and total have the following menu structure for routine work:

Main Menu Level #2 Level #3 Level #4

Flow rates Indicated vol rate Indicated vol rate

Gross volume rate Gross volume rate

Ind std vol rate Ind std vol rate

Gross std vol rate Gross std vol rate

Mass rate Mass rate

Net oil/water rate Oil vol rate Oil vol rate

Oil std vol rate Oil std vol rate

Oil mass rate Oil mass rate

Water vol rate Water vol rate

Water std vol rate Water std vol rate

Water mass rate Water mass rate

VCF VCF

CCF CCF

Flow totals Ind volume total Ind volume total

Gross volume total Gross vol total

Ind std vol total Ind std vol total

Gross std vol total Gross std vol total

Mass total Mass total

Net oil & water Oil vol total Oil vol total

Oil std vol total Oil std vol total

Oil mass total Oil mass total

Water vol total Water vol total

Water std vol total Water std vol total

Water mass total Water mass total

Alarm total Alarm total

Turbine errors Main turb Errors


7951 2510 (Ch12/BE) Page 12.3

12.1.2 Data Map: Density, Base density and Specific Gravity

Density, Base density and Specific Gravity have the following menu structure for routine work:


Density Prime density Prime txdr density

Prime dens select Prime den selected

Meter density Meter density

Densitometer Prime txdr density Prime txdr density

Selected density Prime den selected

Density A Density A value

Density B Density B value

Viscometer Visc prime density Visc prime density

Selected viscomtr Prime Dyn visc sel

Visc A density Density C value

Visc B density Density D value

API referral Compress F API compress F b->m

Alpha API alpha b->m

CTL CTL

CPL CPL

Degrees API Degrees API

Net oil/water dens Base oil density Base density oil

Base water density Base den water (net)

Prime oil density Prime oil density

Prime water dens Prime density water

Meter oil dens Line density oil

Meter water dens Line density water

Oil SG Oil specific gravity

Oil degrees API Oil degrees API

Prime dens limits Prime dens HI lmt Density HI limit

Prime dens LO lmt Density LO limit

Base density / SG Base density Base density value

Specific gravity SG Value

Water density Water density (SG)

API referral Compress F API compress F d->b

Alpha API alpha d->b

CTL CTLd

CPL CPLd

Limits Base dens limits Base dens HI limit

Base dens LO limit

SG limits SG HI limit

SG LO limit


Page 12.4 7951 2510 (Ch12/BE)

12.1.3 Data Map: Viscosity Viscosity measurements have the following menu structure for routine work:


Viscosity Prime viscosity Dynamic Prime dynamic visc

Kinematic Prime kinematic visc

Selected viscomtr Prime dyn visc sel

Viscosity A Dynamic Dynamic visc A

Kinematic Kinematic visc A

Q factor Q factor visc 3

Range Visc 3 current range

Viscosity B Dynamic Dynamic visc B

Kinematic Kinematic visc B

Q factor Q factor visc 4

Range Visc 4 current range

Meter kin viscosity Meter kinematic visc

Base kin viscosity Base kinematic visc


7951 2510 (Ch12/BE) Page 12.5

12.1.4 Data Map: Temperature and pressure Temperature and pressure measurements have the following menu structure for routine work:


Temperature Meter temperature Meter temperature

Dens temperature Prime dens temp Prime dens temp Density A temp Density A temp Density B temp Density B temp

Visc temperature Prime visc temp Prime visc temp Selected viscomtr Prime Dyn visc sel Visc A temperature Visc A temperature Visc B temperature Visc B temperature

Prover temperature Prover inlet temp Prover inlet temp Prover outlet temp Prover outlet temp

Base temperature Base temperature

Absolute zero Absolute zero

Limits Meter temperature High limit Low limit Step limit Density A temp High limit Low limit Density B temp High limit Low limit Prover inlet temp High limit Low limit Prover outlet temp High limit Low limit Viscosity temp A High limit Low limit Step limit Viscosity temp B High limit Low limit Step limit Pressure Meter pressure Meter pressure

Dens pressure Density pressure

Base pressure Base press value

Equilibrium press Equilibrium press

Prover pressure Prover inlet press Prover inlet press Prover out press Prover outlet press Prv plenum press Plenum press value

Limits Meter pressure High limit Low limit Step limit Prover Inlet press High limit Low limit Prover out press High limit Low limit


Page 12.6 7951 2510 (Ch12/BE)

12.1.5 Data Map: Smaller topics

Smaller topics have the following menu structure for routine work:


Special equations Special eq 1 value Special equation 1

Sediment & Water Prime BSW Prime BSW% Prime BSW%

Prime volume Oil% Prime volume oil%

Prime BSW analyser Prime BSW value

BSW prime selected

BSW A value

BSW B value

Prime BSW limits Prime BSW HI limit

Prime BSW LO limit

Base BSW Mass water% Mass water%

Mass oil% Mass oil%

Water mass% limits Water mass% HI lmt

Water mass% LO lmt

Std vol water% Std volume water%

Std vol oil% Std volume oil%

Water std vol% lmt Water SVol% HI lmt

Water SVol% LO lmt

Meter run BSW Meter BSW% Meter BSW%

Meter volume oil% Meter volume oil%

Meter BSW limit Meter BSW HI limit

Meter BSW LO limit

Meter CSW% Meter CSW

Password Enter password

Time Time and date Time and date

Set cycle time Target cycle time

Actual cycle time Actual cycle time

System idle time Idle cycle time


7951 2510 (Ch12/BE) Page 12.7

12.2 Checking the performance of the 7951 machine If you want to check that the external connections are working properly, the <Health Check> facility can help you. It shows, for each external connection:

The name of the input or output. The value of the data. The units for the data. Whether the data is live or set.

If the data is live but the value appears to be unusually high or low, this may be because the external connection is not working properly.

12.2.1 Data Map: Health check The <Health Check> feature has the following menu structure: (Part 1 of 2)


Health check Inputs Analog inputs Analog input 1

Analog input 2

: : :

mA input 10

Time period inputs Time period input 1

Time period input 2

Time period input 3

Time period input 4

7827 period I/P 1b

7827 period I/P 2b

7827 period I/P 3b

7827 period I/P 4b

Flow meter inputs Turbine

Orifice

Status inputs Status in [1-16]

Pulse inputs Pulse input 1

Pulse input 2

HART inputs HART board status

HART 1 value

HART 2 value

: : : HART 8 value

Strainer input Status

DP value

Outputs mA outputs mA Output 1

mA Output 2

: : :

mA Output 8

Status outputs Status out [1-16]


Page 12.8 7951 2510 (Ch12/BE)

Health Check Menu Structure (Part 2 of 2)


Flow meter details Turbine Flow meter freq

Meter factor

K factor

Pulse error count

Orifice Beta

Discharge coeff

Expand factor

Vel of approach

Reynolds number

Corr pipe diameter

Corr orif diameter

Press loss value

Mass rate K factor

Pressure ratio

Totals Standard increment Ind vol total

Gross volume total

Ind std vol total

Gross std vol total

Mass total

Net oil & water

Turbine errors

Alarm total

Maintenance Totals

Increments

User Alarms Alarm state: ABXY


7951 2510 (Ch12/BE) Page 12.9

12.3 Printed reports This section explains how the 7951 can print a variety of sytem reports.

12.3.1 Types of report There are a variety of printed reports to choose from.

Report name (as displayed) Content of report

Current report This shows settings and values of up to 20 data locations that have been set-up in a user-defined list. (Refer to Chapter 9 for a guide to this report)

Alarm report Contents of the Historical Alarm Log and attributes of up to 20 user-nominated parameters.

Event report Contents of the Historical Event Log and attributes of up to 10 user-nominated parameters.

Config report Application configuration details and attributes of up to 10 user-nominated parameters.

Current QTR Current batch transaction record and attributes of up to 10 user-nominated parameters. (See “Batching” in Chapter 18)

Previous QTR Previous batch transaction record and attributes of up to 10 user-nominated parameters. (See “Batching” in Chapter 18)

Prover report General Proving Session Report. (See Chapter 16A for a sample print-out)

Brooks prove rpts Brooks Compact Proving Session Report

Alarm log The “Alarm” trigger Archive. (See Chapter 9 for details of Archiving)

Manual log The “Manual” trigger Archive. (See Chapter 9 for details of Archiving)

Daily log The “Daily” trigger Archive. (See Chapter 9 for details of Archiving)

Interval log The “Interval” trigger Archive. (See Chapter 9 for details of Archiving)

Reports can be enhanced to include header and footer information. (See PRINT MENUs: <”Header & footer”> and <”Define reports”>)

12.3.2 Printing a report

Reports have to be printed out individually. Each print request involves selecting a report name (description) from a fixed list of all reports. The contents of that report is then transmitted through a serial communications port that has been set-up for connection to an ASCII compatible output device.

The “World” security level prevents everyone from requesting a report to be printed. However, all other security levels can be used to request any of the reports that are listed above. To find out about how to change security level, refer to the “Password and Security” section in Chapter 11.

How to print a report using the front panel keyboard

Follow these instructions: 1. Ensure that at least one serial communications port is configured for printing and the port is suitably

connected to either an ASCII printer or a PC running a terminal emulation program. (Note: The set-up on the output device outside the scope of this Operating Manual) .

2. Press the PRINT MENU button.

3. Navigate to this menu: <“Print report”>.


Page 12.10 7951 2510 (Ch12/BE)

4. Edit the option (value) to be one of the report descriptions from the fixed list.

5. Watch the report appear either on the ASCII output device.

How to print a report by other methods

Method #1: ‘Remote’ Print via MODBUSA MODBUS networked device can directly manipulate database locations of the 7951 machine. With this method, a MODBUS ‘write’ command message can be used to write a report identification code to the parameter <”Print”>. The identified report is then be transmitted as normal.

Chapter 7 features worked examples of supported MODBUS commands that can be very easily adapted for this purpose.

It will be necessary to know the location number of “Print Report” for part of the command sequence. This can be done by pressing the PRINT-MENU button, searching the menu structure and then, once found, pressing the ‘a’ button.

Follow these instructions: 1. Ensure that a serial communications port is configured for printing and the port is suitably connected to

either an ASCII printer or a PC running a terminal emulation program. (Note: The set-up on the output device outside the scope of this Operating Manual)

2. Transmit a MODBUS write command to the 7951 machine. Report Identification Codes are as shown Table 12.1.

3. Watch the report appear either on the ASCII output device.

Table 12.1: Report Selection Codes

Value Report Selected

0 "None" 1 "Current report" 2 "Alarm report" 3 "Event report" 4 "Config report" 5 "Current QTR" 6 "Previous QTR" 7 "Prover report" 8 “Brooks prove rpts” 9 "Alarm log"

10 "Manual log" 11 "Daily log" 12 "Interval log"


7951 2510 (Ch12/BE) Page 12.11

(How to print a report by other methods continued…)

Method #2: ‘Remote’ Print via Digital (Status) InputBy default, Status Input 4 can be used by an external system to request a printout of the “Current” report.

Follow these instructions: 1. Ensure that a serial communications port is configured for printing and the port is suitably connected to

either an ASCII printer or a PC running a terminal emulation program (Note: The set-up on the output device outside the scope of this Operating Manual)

2. Ensure that the Status Input 4 is suitably wired to the external system that will activate it

It is possible to modify attributes of a digital (status) input: (a) Logic sense: Choose between “Positive Logic” (default) or “Negative Logic” (b) Mode: Choose between “Non latched” (default) or “Latched”

Configuration parameters are under: <“Configure”>/<”Inputs”>/<“Status Inputs”> (or similar)

3. Test by activating the digital (status) input.

It is possible to allocate this remote print function to another digital (status) input but care is needed to avoid clashes with the prover requirements (See Chapter 16) and the digital input allocated to selecting maintenance-mode. (Menu: <“Configure”>/<IO physical alloc”>)

12.3.3 Some typical reports

(a) “Current” report with two user-nominated parameters

CURRENT REPORT ================Report printing time: 30/11/2007 15:26:29 Tag number 512510 Software Version 2510 Iss 4.30.00 Indicated vol rate 200.000 m3/hour SET Ind volume total 4039565.849 m3 ******************** END OF REPORT ********************

(b) “Alarm” report with one alarm

ALARM LOGGER REPORT ======================Report printing time: 30/11/2007 15:28:00 Tag number 512510 Software Version 2510 Iss 4.30.00 21/02/2000 13:30:31 OFF * Power fail SYSTEM 20/02/2000 17:17:39 ON * Power fail SYSTEM ******************** END OF REPORT ********************


Page 12.12 7951 2510 (Ch12/BE)

(c) “Event” report with two events

EVENT LOG REPORT ================ Report printing time: 30/11/2007 15:43:44 Event List: ----------29/11/2007 16:46:25 USER, Input channel 1 * New: 0.000 % SET Old: 25.000 % SET 29/11/2007 16:45:30 USER, BSW pcent @ 100% * New: 100.000 % Old: 0.000 % ----------Tag number 512510 Software Version 2510 Iss 4.30.00 Power fail time 29/11/2007 17:17:39 ******************** END OF REPORT ********************

12.4 Giving your 7951 instrument a tag number If you have more than one 7951 you may want to give each instrument a tag number so that, in printed reports for example, you know which one the report refers to.

To allocate an identifier:

1. Select the <Tag number> option on the Main Menu.2. Press the ‘b’ button. (The cursor shifts to the left of the screen) 3. Key in the identifier you want. (This over-types any existing identifier) 4. Press the ‘b’ button again. (The new details shift back to the right of the display).

Chapter 13 Routine maintenance and fault-finding

7951 (Ch13/BD) Page 13.1

13. Routine maintenance and fault finding 13.1 Cleaning the instrument

You can use a cloth or sponge and water clean the outside of the instrument. Do not use caustic cleaning agents or abrasive materials.

13.2 Fault finding Although the instrument is designed to be extremely reliable it is possible that faults may arise at some time or another. The fault-finding charts show the most likely faults and explain how to trace their causes and put them right. If you cannot cure a fault yourself, contact your supplier or the manufacturers for help.

Note: Use the “Health Check” facility on the 7951 to monitor a variety of measurement parameters,

including time period inputs, analogue inputs and status inputs and outputs. This can be used as a diagnostic aid if the system seems to be faulty.


Page 13.2 7951 (Ch13/BD)

Is thetransmitter

receiving powerfrom the

7951?

Isthe 7951

configuredcorrectly

?

Is thetransmitter

sending currentto the 7951

?

Has itever beendisplayed

?

YES

YES

YES

YES

7951's Connector/Power Supply Boardis probably faulty

Correct theconfiguration

The 7951's inputcircuit is probablyfaulty

The transmitter orits configurationis probably faulty

NO

NO

NO

NOIs the

transmitter'sfield wiring

correct?

Check the field wiringagainst the wiringschedule

The field wiringis faulty

Wire the transmitterup according to thewiring schedule

Replace the fieldwiring to thetransmitter

Change theConnector Board

Refer to thetransmitter's manualfor more information.

Replace the 7951'sConnector/PowerSupply Board

A reading froma transmitter isnot displayed

NO

YES

PROBLEM:

Figure 11.3: Fault-finding chart 1: No reading from a transmitter

Take great care during this procedure because thepower supply must be ON when you carry it out.


7951 (Ch13/BD) Page 13.3

Hasthe fuse

in the 7951blown

?

Is thesecurity LEDon the 7951

lit?

Is thepower tothe 7951

ON?

YES

YES

7951's Connector/Power Supply Boardis probably faulty

NO

NO

NO

Is the7951's supplyvoltage within

spec?

Turn the power ON

Replace the 7951sConnector/PowerSupply Board

YESThe 7951's DisplayModule is probablyfaulty

Replace the 7951'sDisplay Module

The display is blank

Adjust the voltage sothat it is within spec

NO

PROBLEM:

Replace the fuse byone of the correctrating

YES

Figure 12.2: Fault-finding chart 2: The display is blank


Page 13.4 7951 (Ch13/BD)

Chapter 14 Removal and replacement of parts

7951 (Ch14/BF) Page 14.1

14. Removal and replacement of parts

Warning: Electricity is dangerous and can kill. Disconnect the power supply before making any

connections or dis-assembling the 7951.

14.1 Front Panel Assembly 1. Undo and remove the four screws which secure the Bezel to the case. Withdraw the Front Panel

Assembly to the limits of the connecting wiring then lay it on top of the case.

2. Partially withdraw the Processor Board then disconnect the two connectors from the Processor Board. The Front Panel Assembly is now free.

3. Replace all items by reversing this procedure. Take great care to ensure that the cables are not pinched on re-assembly.

Switch paneland bezel

Display

Front PanelAssembly

Displaycable

PL1 PL2

Display fixing screwsand washers (4 off)

Bezel fixingscrews (4 off)

ProcessorBoard

Case

Figure 14.1: Removing the Front Panel Assembly

14.2 Display 1. Remove the Front Panel Assembly as explained in Section 14.1.

2. Undo and remove the four screws and washers which attach the display to the Front Panel Assembly.

3. If required, unplug the ribbon cable from the display.

4. Replace all items by reversing this procedure.


Page 14.2 7951 (CH14/BF)

14.3 Switch Panel 1. Remove the Front Panel Assembly as explained in Section 14.1

2. Undo the four screws and washers which attach the display to the bezel. Remove the display.

3. Un-solder the flexi cable from the key switch. Remove the spring clip from the switch then withdraw the switch from the case.

4. Undo and remove the four nuts and washers which attach the Switch Panel to the bezel. Lift the Switch Panel away.

5. Replace all items by reversing this procedure.

Bezel

Displayand cable

Display fixing screwsand washers (4 off)

SwitchPanel

Switch Panelfixing nuts andwashers (4 off)

Springclip

Keyswitch

Switchcable

Figure 14.2: Removing the Switch Panel Assembly

14.4 Processor Board 1. Remove the Front Panel Assembly as explained in Section 14.1

2. Pull the Processor Board forwards so that it disengages from the connector at the back of the case. Withdraw the board from the case.


Switch Paneland Bezel

Displaycable

PL1 PL2

Switch panelcable

Power SupplyBoard

ProcessorBoard

MotherBoard

Figure 14.3: Removing the Processor Board and Power Supply Board


7951 (Ch14/BF) Page 14.3

14.5 Power supply board 1. Undo and remove the four screws which secure the Bezel to the case. Withdraw the Front Panel


2. Pull the Power Supply Board forwards so that it disengages from the connector at the back of the case. Withdraw the board from the case.


14.6 Connector Board 1. Remove the Rear Panel Assembly as described in Section 14.9.

2. Remove the Mother Board as explained in Section 14.10.

3. Unscrew the threaded hexagonal spacers on top of the Connector Board, then lift the Connector Board off the studs.


14.7 Fuse 1. Undo and remove the four screws which secure the Bezel to the case. Withdraw the Front Panel


2. Slide the Power Supply Board out of the case.

3. Referring to the diagram, find the fuse and gently prise it out of the fuse holder.

4. Press the replacement fuse into the fuse holder. Make sure that the fuse is of the correct type and rating as specified in Chapter 15.

5. Replace all items in the reverse order of removal. Take great care to ensure that the cables are not pinched on re-assembly.

PowerSupplyBoard

MotherBoard

RearPanel

Top ofinstrumentcase

SocketSK1Fuse

Figure 14.4: Where to find the fuse on the Power Supply Board


Page 14.4 7951 (CH14/BF)

14.8 Back-up battery 1. Ensure that the unit is disconnected from all power supplies.

2. Ensure that a new battery (CR2430) and a thin edged, non-conductive implement are within easy reach.

3. Undo the six captive screws which attach the front panel assembly to the case.

4. Carefully lift the front panel assembly away from the case.

5. Undo the yellow and green Earth lead from the panel. Do not undo the connecting ribbon cables.

6. Locate the back-up battery on the Processor Board.

7. Referring to the diagram below, use a non-conductive implement to gently lever the battery upwards from near the rear of the clip. As soon as the battery lifts up a small amount, gently ease the battery in a horizontal direction away from the holder and the clip. Keep the battery in contact with the clip.

DO NOT LIFT UP THE CLIP MORE THAN NECESSARY TO MOVE THE BATTERY.

8. Keep the battery in contact with the clip until you are prepared to insert a new one.

When the clip loses contact with the battery, there is a maximum of 10 seconds before all configuration and database information is lost.

9. Once prepared, remove existing battery and then slide the new one under the clip and into the holder - observing the polarity symbols. Complete this action within 10 seconds.

10. Replace all items in the reverse order of removal.

Part ofProcessorBoard

Batteryholder

Battery

Clip/contact

Figure 14.5: Where to find the back-up battery on the Processor Board


7951 (Ch14/BF) Page 14.5

14.9 Rear Panel Assembly Warning: It is strongly recommended that in order to ensure continued compliance to EMC directives, you do not attempt to remove the rear panel assembly, but return the 7951 to the factory. Contact us first using the details on the back page.

The instructions given below should only be carried out if it is absolutely necessary.

1. Remove the Front Panel Assembly as explained in Section 14.1

2. Pull the Processor Board forwards so that it disengages from the connector at the back of the case. Withdraw the board from the case.

3. Pull the Power Supply Board forwards so that it disengages from the connector at the back of the case. Withdraw the board from the case.

4. Remove the four screws which secure the Rear Panel Assembly into the case.

5. Withdraw the Rear Panel Assembly from the case, taking care not to bend the metal spring clips on the top and bottom of the Connector Board.

6. Replace all items by reversing this procedure. Take great care to ensure that the cables are not pinched on re-assembly, and ensure that the metal clips are not bent or damaged.

ProcessorBoard

Rear PanelAssemblyfixing screws(4 off)

Power SupplyBoard

MotherBoard

Figure 14.6: Removing the Rear Panel Assembly


Page 14.6 7951 (CH14/BF)

14.10 Mother Board Warning: It is strongly recommended that in order to ensure continued compliance to EMC directives, you do not attempt to remove the rear panel assembly, but return the 7951 to the factory. Contact us first using the details on the back page.

1. Remove the Rear Panel Assembly as described in Section 14.9.

2. Referring to the diagram, undo and remove the six screws and washers which fix the Mother board to the rest of the Rear Panel Assembly.

3. Using a straight pull, carefully lift the Mother Board clear of its four connections to the connector board. The Mother Board is now free.

4. Replace all items by reversing this procedure. Take great care to ensure that the cables are not pinched on re-assembly, and ensure that the metal clips are not bent or damaged.

COMPLETE ASSEMBLY DISMANTLED ASSEMBLY

MotherBoard

Threadedspacers

ConnectorBoard

RearPanel

Earth studand fixings

Screws andwashers

Rearpanel

Plainspacers

Figure 14.7: Removal of the Mother Board and Connector Board

Chapter 15 Assembly drawing and parts list

7951 (CH15/CA) Page 15.1

15. Assembly drawing and parts list

15.1 What the drawing and parts list tell you The drawing and parts list show those parts of the 7951 which you can obtain as spares. To identify an item:

1. Find the item on the appropriate assembly drawing

2. Note the Item Number by the side of it.

3. look up the Item Number on the parts list. The parts list tells you:

The Part Number for the item.

A description of the item.

The quantity of the item that appears on the drawing.

15.2 How to obtain spare parts You can obtain spare parts from the supplier from whom you bought the instrument, or from the factory. In either case, you must state on your order:

Your name, address and telephone or fax number.

A description of the parts you want.

The part numbers of the items you are ordering.

The quantity of each item.

Contact details for the factory are on the back page.


Page 15.2 7951 (CH15/CA)

Figure 15.1: Diagram for identifying and ordering spares


7951 (CH15/CA) Page 15.3

Item no. Part number Description Quantity

1 79513701A Instrument case 1

2 79510219AVV Front panel (Supplied Fully Assembled With Cable) 1

3 79510503BVV Motherboard 1

4 79510505AVV 79510504BVV

Connector board (Klippon connectors) Connector board (D-type connectors)

1 1

5 79513702A 79513706A

Rear Panel (Klippon connectors) Rear panel (D-type connectors)

1 1

6 79510502JVV 79510502KVV

Processor board for 7951 flow computer with 16 MHz software Processor board for 7951 flow computer with 24 MHz software 1

7 79510501CVV Power supply board 1

8 411129010 M3 crinkle washer 6

9 79513710A 15-way cable 1

10 400001930 M4 thumb nut 1

11 410031020 M4 hexagonal full nut 2

12 411029020 M4 plain washer 2

13 412011420 Nylon spacer: 3.5mm ID x 8mm long 6

14 41530070 Hexagonal spacer: M3 x 13mm long 6

15 406803060 M3 x 6mm pan-head screw 6

16 411129020 M4 crinkle washer 2

17 406902460 M3 x 8mm pan-head screw 8

18 360106230 2 Amp glass fuse 1

19 800400380 Lithium battery CR2430 1


Page 15.4 7951 (CH15/CA)

Chapter 16(a) Flowmeter Proving

7951 2510 (CH16A/CB) Page 16A.1

16A. Flowmeter Proving 16A.1 Introduction to this Chapter

This chapter explains how a 7951 instrument (with D-type connectors) can be set-up to use a pipe-based Prover to calibrate a volumetric/mass meter.

The flowmeter of a metering-run (stream) can be proved ‘locally’ with one 7951 performing both ‘Proving’ and ‘Metering’ functions. Alternatively, the flowmeter of a metering-run (stream) can be proved ‘remotely’ with one 7951 performing ‘Proving’ functions and other 7951† instruments performing metering-run (stream) functions.

Proving functions may be performed either from the front panel of the main 7951 or over a MODBUS network. In both cases, the result of proving a flowmeter is a calculated factor - ‘meter factor’ (MF) or ‘K factor (KF) - that will maintain the accuracy of flow measurements.

Sections have been organised as follows:

Section Purpose of section 1st. Page

Overview of a ‘prove run’ for each Pipe Prover. The emphasis is on how the 7951 functions under normal conditions.

16A.2 16A.2.1 Flowmeter Proving 16A.2.2 Uni-directional pipe Prover 16A.2.3 Bi-directional pipe Prover 16A.2.4 Brooks Compact (Small Volume) Pipe Prover

16A.216A.216A.516A.8

16A.3 Explanation of “Double Time Pulse Interpolation”. 16A.10

16A.4 The Prover Calculations 16A.11

16A.5

Details and diagrams for proving related connections: 16A.5.1 Status Inputs 16A.5.2 Status Outputs 16A.5.3 Analog Inputs 16A.5.4 Pulse (Turbine) Inputs 16A.5.5 ‘Remote’ Proving Connection Summary

16A.1616A.1916A.2116A.2116A.21

16A.6 Valve control and monitoring (all supported Provers) 16A.22

16A.7 Configuration tasks for defining Prover details and setting up a Prove session 16A.27

16A.8 How to operate a ‘prove session’ and then view the results 16A.40

16A.9 Archiving of proving information 16A.52

16A.10 Prover reporting 16A.54

16A.11 Trouble-shooting Guide – Alarms and On-screen Messages 16A.57

16A.12 Miscellaneous Reference Sections – Flowcharts and Timing Diagrams 16A.58

† The flow computers must be running the same release of the software.


Page 16A.2 7951 2510 (CH16A/CB)

16A.2 Provers and pipe proving methods This section gives an overview of how the 7951 instrument works with various Pipe Provers.

16A.2.1 Flowmeter Provers

There are three basic types of conventional flowmeter Provers:

1. Tank Prover This was the first ever type of Prover to be used to calibrate a flow meter. It is not used very often today.

2. Master Meter Prover This type allows a metering-run flowmeter to be proved against another in-frequently used meter

3. Pipe Prover This is the most commonly used type today.

Sections 16A.2.2 to 16A.2.3 contain a 7951-biased overview of a simple, yet typical, prove run for each supported Prover. Details, such as time limit considerations and pulse interpolation, are in section 16A.3.

16A.2.2 Uni-directional pipe Prover

Brief overview of a prove run After selecting a metering-run with the ‘Meter to prove’ location and a flow computer (“device”) to control the prove, it is necessary to select the ‘prove start’ command in the 7951 ‘prover control’ location. This command causes the prover to be checked for a ‘ready to prove’ state. This state is essential to progress the session with valve alignments and must be maintained during a prove session.

Metering-run valves and Prover valves must then be positioned to allow flow to enter the prover-loop. This valve alignment may be performed automatically, with a sequence of commands (as pulses) being issued by the 7951 to valve controllers. Alternatively, the alignment must be performed by another system with the operator confirming to the 7951 that valves are aligned.

Flow enters the prover-loop through the Prover Isolation (Inlet) valve after valves are aligned.

Tests for stable conditions are performed at this time. Temperature, pressure and flow rates are sampled from two flow points (at the Prover and at the Turbine) over a user-definable amount of time. The difference between comparable measurements at the two flow points must all be within user-definable limits on ten successive occasions for the Prover Loop to be considered stable. For example, the difference between the line pressure and prover pressure is compared with a pressure difference limit.

The 7951 signals the Prover to launch the ‘displacer’ in the direction of flow if the 7951 considers conditions to be stable.

Detector switch 'C'

Calibratedvolume

Sphere

Detector switch 'A'

Spherehandling

interchange

Proverloop Prover inlet

valve (Open)

Streamblockvalve

(Closed)

Flow

Prover outletvalve (Open)

LaunchingTee

LaunchingTee

Figure 16.1: Uni-directional Pipe Prover with a single metering-run


7951 2510 (CH16A/CB) Page 16A.3

This type of prover uses a sphere to displace flow, in one direction, through a prover-loop and measuring section. Detector switches are positioned along the measuring section so that they de-limit a known (calibrated) volume. The flow forces a launched sphere on a one way trip past these detectors.

In the illustration below, a sphere has been launched from the handling interchange. The sphere is travelling with the flow.

Detector switch 'C'

Calibratedvolume

Launchedsphere

Detector switch 'A'

Spherehandling

interchange

Proverloop Prover inlet

valve (Open)

Streamblockvalve

(Closed)

Flow


LaunchingTee

LaunchingTee

The first detector switch (nominated as ‘A’) transmits a pulse to the 7951 as soon as the sphere ‘displacer’ reaches it. The 7951 receives this pulse and starts counting pulses from a connected flow meter.

Flow

Detector'C'

Detector'A'

Calibrated volume

7951

Stage 1 : Sphere launched towards detectors Stage 2 : Sphere reaches first detector

Flow

Detector'C'

Detector'A'

Calibrated volume

7951

Pulses continue to be counted by the 7951 until the sphere ‘displacer’ reaches the final detector switch (nominated as ‘C’).

Stage 3 : Sphere approaches the final detector

Flow

Detector'C'

Detector'A'

Calibrated volume

Stage 4 : Sphere reaches the final detector

Flow

Detector'C'

Detector'A'

Calibrated volume

79517951

The sphere then travels further along the Prover Loop until an ‘Interchange’ mechanism is encountered. This mechanism returns the sphere to a position ready for launching at the next proving run.

A prove run is now complete.


Page 16A.4 7951 2510 (CH16A/CB)

The pulses accumulated, over one volume sweep, may be less than 10,000 and, therefore, not sufficient to calculate the meter factor with an accuracy of +/- 0.01% (as required by ISO7278 / BS6866 part 3). Therefore, a method known as “double-timing pulse interpolation” is used to overcome this problem - see section 16A.3 for details.

A prove session consists of a series of prove runs. The number of consecutive runs is user-definable. Calculations at the end of a run determine a ‘meter factor’ (MF) for that run. The MF is checked against user-defined limits, to determine if it is a ‘good’ or ‘bad’ factor value.

At the end of a successful prove session, the final (session) MF is determined from the average pressures, temperatures and pulse accumulation (interpolated pulses). The session MF is checked against user-defined limits, to determine if it is a ‘good’ or ‘bad’ factor value. If it is a ‘good’ factor value, it is offered to the operator for acceptance; a ‘bad’ session MF is immediately discarded. If the MF is accepted, it is used in subsequent flow calculations. Otherwise, the MF is discarded and the previous pre-session value is re-used in subsequent flow calculations.


7951 2510 (CH16A/CB) Page 16A.5

16A.2.3 Bi-directional pipe Prover

Brief overview of a prove run After selecting a metering-run with the ‘Meter to prove’ location and a flow computer (“device”) to control the prove, it is necessary to select the ‘prove start’ command in the 7951 ‘prover control’ location. This state is essential to progress the session and must be maintained during the entire prove session.

Metering-run valves and Prover valves must then be positioned to allow flow to enter the Prover loop. This valve alignment may be performed automatically, with a sequence of commands (as pulses) being issued by the 7951 to valve controllers. Alternatively, the alignment must be performed by another system with the operator confirming to the 7951 that valves are aligned.

Flow enters the Prover Loop through a 4-way diverter valve after valves are aligned. This 4-way diverter valve is controlled and monitored by the 7951. It is positioned to direct flow in one of two directions around a Prover Loop and measuring section.

Tests for stable conditions are performed at this time. Temperature, Pressure and Flow rates are sampled from two flow points (at the Prover and at the Turbine) over a user-definable amount of time. The difference between comparable measurements at the two flow points must all be within user-definable limits on ten successive occasions for the Prover Loop to be considered stable. For example, the difference between the Line Pressure and Prover Pressure is compared with a pressure difference limit.

The 7951 signals the Prover to launch the ‘sphere’ in the direction of flow if the 7951 considers conditions to be stable. The mechanism for launching the sphere varies. Either a hydraulic ram is used or the 4-way diverter valve is rotated so that the sphere is no longer held at one end by the flow.

Calibratedvolume

Spherelauncher

Launchedsphere

4-waydivertervalve

Proverloop

Proverinletvalve

(Open)

Streamblockvalve

(Closed)

Spherelauncher


DetectorSwitch 'B'

DetectorSwitch 'A'

DetectorSwitch 'C'

DetectorSwitch 'D'

Figure 16.2: Bi-directional type prover with a single metering-run

The bi-directional type of prover uses a sphere to displace flow, twice, through a “prover loop” and measuring section. Detector switches are positioned along the measuring section so that they de-limit a known (calibrated) volume. Often, there are two pairs of detector switches - this allows the calibrated volume to be selected. Support is provided by the ‘Proving’ 7951 through a configurable data location.

In the illustrations above and below, the sphere has been launched and travels with the flow. The first detector switch (nominated as ‘A’) sends a pulse to the 7951 as soon as the sphere reaches it. The ‘Proving’ 7951 receives this pulse and starts counting pulses from a connected flow meter.


Page 16A.6 7951 2510 (CH16A/CB)

Flow

Detector'C'

Detector'A'

Calibrated volume

7951

Stage 1 : Sphere launched towards detectors Stage 2 : Sphere reaches first detector

Flow

Detector'C'

Detector'A'

Calibrated volume

7951

The sphere continues to travel through the calibrated volume until it reaches the final detector switch (nominated as ‘C’). A pulse is then sent to the 7951 and this halts the pulse count.

Stage 3 : Sphere approaches the final detector

Flow

Detector'C'

Detector'A'

Calibrated volume

Stage 4 : Sphere reaches the final detector

Flow

Detector'C'

Detector'A'

Calibrated volume

79517951

When the sphere reaches the end of the Prover Loop, the flow direction is reversed by re-positioning the 4-way diverter valve. The force of the reverse flow launches the sphere back towards the original start position.

Calibratedvolume

Spherelauncher

Re-launchedsphere

4-waydivertervalve

Proverloop

Proverinletvalve

(Open)

Streamblockvalve

(Closed)

Spherelauncher


DetectorSwitch 'B'

DetectorSwitch 'D'

DetectorSwitch 'C'

DetectorSwitch 'A'

Figure 16.3: Bi-directional type prover with a single metering-run - sphere return journey

Again, on encountering the first detector switch (now ‘C’), a pulse is transmitted to the 7951 and this starts another flow meter pulse count. The pulse count stops when the final detector (now ‘A’) is reached and it transmits a pulse to the 7951. Flow takes the displacer into the launcher.

This completes a single prove run.


7951 2510 (CH16A/CB) Page 16A.7

The pulses accumulated, over two volume sweeps, will normally be at least 10,000 and, therefore, sufficient to calculate the ‘meter factor’ with an accuracy of +/- 0.01% (as required by ISO7278 / BS6866 part 3). Pulse interpolation is not required in this case. However, at present, double-time pulse interpolation is applied.

A prove session consists of a series of prove runs. The number of consecutive runs is user-definable. Calculations at the end of a run determine a ‘meter factor’ (MF) for that run. The MF is checked against user-defined limits, to determine if it is a ‘good’ or ‘bad’ factor value.



Page 16A.8 7951 2510 (CH16A/CB)

16A.2.4 Brooks Compact (Small Volume) Pipe Prover

Overview of a prove run After selecting a metering-run with the ‘Meter to prove’ location and a flow computer (“device”) to control the prove, it is necessary to select the ‘prove start’ command in the 7951 ‘prover control’ location. This command causes the Prover to be commanded by the 7951 to retract the piston to the stand-by (start) position.

Metering-run valves and Prover valves must then be positioned to allow flow to enter the Prover Loop. This valve alignment may be performed automatically, with a sequence of commands (as pulses) being issued by to valve controllers by a 7951. Alternatively, the alignment must be performed by another system with the operator confirming to the 7951 that valves are aligned.

Flow enters the Prover Loop after valves are aligned.

Tests for stable conditions are performed next. Temperature, Pressure and Flow rates are sampled from two flow points (at the Prover and at the Meter) over a user-definable amount of time. The difference between comparable measurements at the two flow points must all be within user-definable limits on ten successive occasions for the Prover Loop to be considered stable. For example, the difference between the Line Pressure and Prover Pressure is compared with a pressure difference limit.

Plenum pressure is monitored over a user-definable length of time after tests for stable conditions. The 7951 can issue either a ‘charge command’ signal or a ‘vent command’ signal to the Prover to adjust this pressure if it is not at a user-defined level.

The ‘Proving’ 7951 signals the Prover to launch the piston in the direction of flow if: (a) the 7951 considers conditions to be stable and (b) Plenum pressure is at a required level.

In the simplified illustration below, the piston has been launched and is travels in the flow direction. The first detector switch (nominated as ‘A’) sends a pulse to the 7951 as soon as the piston reaches it. The ‘Proving’ 7951 receives this pulse and starts counting pulses from a connected flowmeter.

Detector 'A'

Detector'C'

Calibrated volume

7951

Flow

InletOutlet

The piston continues to travel through the calibrated volume until it reaches the final detector switch (nominated as ‘C’). A pulse is then sent to the ‘Proving’ 7951 and this halts the pulse count.

Detector 'A'

Detector'C'

Calibrated volume

7951

Flow

InletOutlet


7951 2510 (CH16A/CB) Page 16A.9

When the piston reaches the end of the Prover Loop, the run is completed. The piston is automatically retracted back to the ‘standby’ (start) position for when the Prover receives another ‘start prove’ signal from the ‘Proving’ 7951.

The pulses accumulated, over one volume sweep, will be less than 10,000 and, therefore, not sufficient to calculate the meter factor with an accuracy of +/- 0.01% (as required by ISO7278 / BS6866 part 3). Therefore, a method known as “double-timing pulse interpolation” is used to overcome this.

A prove session consists of a series of runs. A run consists of passes. A pass is one ‘piston flight’. The number of consecutive passes and runs is user-definable.

Calculations at the end of a run determine a ‘meter factor’ (MF) for that run. The MF is checked against user-defined limits, to determine if it is a ‘good’ or ‘bad’ factor value.



Page 16A.10 7951 2510 (CH16A/CB)

16A.3 Double-time Pulse Interpolation This method is used by the 7951 for determining an accurate pulse count for the ‘Meter factor’ calculation. All supported pipe provers must use this method.

T1

T2

etc.

Pulse train from a flow meter

Start and stop pulse(from detector switches)

0 1 N

Ignored in favour ofprevious pulse

B E

Ignored in favour ofnext pulse

2 3

Figure 16.4: Timing for double-time pulse interpolation (positive edge detection)

‘T1’ is the accurate measurement of the time‡ between the rising edge (or falling edge) of the start pulse (nominated as ‘B’) and the rising edge (or falling edge) of the stop pulse (nominated as ‘E’).

Rising (positive) edge detection is shown in the figure above. However, the polarity of the edge detection process is software selectable.

‘T2’ is the accurate measurement of the time taken between ‘N’ complete (or even partial) pulses that fall within the ‘T1’ time frame. Pulses that are fully outside the ‘T1’ time frame are not counted.

After a prove-run is completed, the 7951 carries out calculations to correct the raw pulse count:

First, using the equation: f NT

u1

2

Where: f1 = frequency of incoming pulses during time frame ‘T2’. {Parameter: <”Flow meter frequency”>}

Nu = Uncorrected pulses count during time frame ‘T2’…... {Parameter: <”Prv run pulse count”>}

T2 = Time reference, ‘T2’……………………………………. {Parameter: <”Prv run TDVOL”>}

Now, using the equation: f NT

c2

1 and re-arranging it so that N f Tc 2 1*

Where: Nc = Corrected pulse count (as used in section 16A.4)….. {Parameter: <”Prv run corr pulse”>}

f2 = f1 (frequency of pulses from flowmeter)…………..... {Parameter: <”Flow meter frequency”>}

T1 = Time reference, ‘T1’……………………………..……… {Parameter: <”Prv run TDFMP”>}

‡ This is sometimes referred to as the “flight time”.


7951 2510 (CH16A/CB) Page 16A.11

16A.4 The Prover Calculations This section lists all the major proving calculations § that are performed after each prove-run.

However, it is the results from the end-of-session calculations that are important. This is emphasised with equation terms having references to the corresponding Parameter in the session part of a Prover Archive.

Turn to page 16A.52 for information about the “Prover Archive”.

16A.4.1 Volumetric Prover Proving of a Volumetric Meter (by Volume)

Calculation PRV#1: New ‘Meter Factor’

The ‘Meter factor’ is a result of the liquid flowmeter proving process. This factor is used when calculating the Gross Volume flow rate at the flow metering point.

Using: MFNew = GSVISV

p

m

Where: MFNew = New calculated ‘Meter factor’……………….. {Parameter: <”Prv new meter factor”>}

GSVP = Gross Standard Volume (Prover)………….. {See next page}

ISVm = Indicated Standard Volume (Meter)………... {See Calculation PRV#4 on next page}

Calculation Notes: 1. The new ‘Meter factor’ is always calculated at the end of a successful session. It is then shown in the

session part of the Prover Archive even if it is not offered for acceptance or offered but then rejected. 2. The ‘Proving’ 7951 (or the combined ‘Metering/Proving’ 7951) will be configured to either offer the new

‘Meter factor’ or offer the new ‘K factor for acceptance to replace an existing meter-run (stream) value. 3. The replaced ‘Meter factor’ value is stored in the session menu at the <”Prv old meter factor”>

parameter

Calculation PRV#2: New ‘K Factor’

The ‘K factor’ is a result of the liquid flowmeter proving process. This factor is used when calculating the Indicated Volume flow rate at the flow metering point.

Using: KFNew = KF

MFOld

New

Where: KFNew = New calculated ‘K factor’……….……………. {Parameter: <”Prover new K factor”>}

KFOld = Previous calculated ‘K factor’…….…………. {Parameter: <”Prover old K factor”>}

MFNew = New calculated ‘Meter factor’………..…….... {See Calculation PRV#1 above}

Calculation Notes: 1. The new ‘K factor’ is always calculated at the end of a successful session. It is then shown in the

session part of the Prover Archive even if it is not offered for acceptance or offered but rejected. 2. The ‘Proving’ 7951 (or the combined ‘Metering/Proving’ 7951) will be configured to either offer the new

‘K factor’ or offer the new ‘Meter factor for acceptance to replace an existing metering-run (stream) value.

§ Implemented in accordance with section 12.2.7.6 of Chapter 12 from the API Standard (August 1987).


Page 16A.12 7951 2510 (CH16A/CB)

Calculation PRV#3: Corrected Prover Volume

The base (calibrated) volume must be corrected for temperature and pressure conditions in the Prover.

Using: GSVp = Vc Ctlp Cplp* *

Where: GSVP = Corrected Prover Volume (m³)….……………………{Parameter: <”Prv corr prover vol”>}

Ctlp = Correction factor for effect of temperature on fluid in the Prover……..…..…..…………… ………………………………………………………….……….….{Parameter: <”Prv CTLP”>}

Cplp = Correction factor for effect of pressure on fluid in the Prover…..…………..………….…… ………………………………………………………….…………..{Parameter: <”Prv CPLP”>}

And: Vc = Vb Cts Cpsp p* *

Where: Vc = Corrected calibrated volume (m³)……………………………………..…………{Not in menu}

Vb = Base Volume of Prover (m³)…………………..……….…..{Parameter: <“Prover volume”>}

Ctsp = Temperature correction factor for steel…….…………………….{See Calculation PRV#5}

Cpsp = Pressure correction factor for steel………….……………………{See Calculation PRV#6}

Calculation Note: 1. The values of Ctlp and Cplp are generated using the same method for generating Ctl and Cpl on the

‘Metering’ 7951 (or the combined ‘Metering/Proving’ 7951). Ctl and Cpl are both generated by the API

referral of the Base Density value to metering conditions. The ‘Metering’ 7951 must perform that API

referral calculation for the ‘Proving 7951’ to then calculate Ctlp and Cplp to proving conditions. [Reference to API Standard: Sections 12.2.5.3 and 12.2.5.4]

Calculation PRV#4: Liquid Volume Correction

The volume (density) of the liquid is going to be different at the flowmeter if the temperature and pressure conditions at the flowmeter are not identical to the temperature and pressure conditions at the pipe prover.

Hence, another volume correction factor is required.

Using: ISVm = IV C Ctlm plm* *

Where: ISVm = Corrected Metered Volume………………..……… {Parameter: <”Prv corr metered vol”>}

Ctlm = Correction factor for effect of temperature on fluid at the flowmeter…………..…………… …………………………………………………………...……..….{Parameter: <”Prv CTLM”>}

Cplm = Correction factor for effect of pressure on fluid at the flowmeter…………...………….…… ……………………………..………………………….……..…….{Parameter: <”Prv CPLM”>}

And: IV = m

CKFN

Where: IV = Meter Volume (in m3)………...…………………….. {Parameter: <”Prv metered volume”>}NC = Interpolated pulse count *…………………….………...{Parameter: <”Prv interp pulses”>}

mKF = The existing factor from the ‘Metering’ 7951 (in pulse/m3)……..…………………….. …………………………………………………………..{Parameter: <”Prover old K factor”>}

* This is the average when using a Brooks Prover; it is not averaged when using other Pipe Provers.


7951 2510 (CH16A/CB) Page 16A.13

Calculation Notes: 1. The values of Ctlm and Cplm are generated using the same method for generating Ctl and Cpl on the

‘Metering’ 7951 (or the combined ‘Metering/Proving’ 7951). Ctl and Cpl are both generated by the API referral of the Base Density value to metering conditions. The ‘Metering 7951’ must perform that API referral calculation for the ‘Proving 7951’ to be able to calculate Ctlm and Cplm .

[Reference to API Standard: Sections 12.2.5.3 and 12.2.5.4]2. The NC term represents an average of the interpolated pulse counts from all of the consecutive good

(passed) prove-runs. The method for calculating an interpolated (corrected) pulse count is explained on page 16A.10.

Calculation PRV#5: Calibrated Volume Temperature Correction These corrections compensate for thermal and mechanical expansion of the pipe prover.

(PRV#5a) Temperature correction for pipe material of Bi-directional and Uni-directional Prover

Using: Ctsp = 1 e t tb*

Where: Ctsp = Temperature correction factor for steel………... {Parameter: <“Prv CTS”>}

t = Average of temperatures at prover valves…….. {Parameter: <“Prv ave prover temp”>} e = Expansion coefficient (PPM/°C)………………... {Parameter: <“Prv expansion coeff”>} tb = Calibration Temperature of Prover……………... {Parameter: <“Prover cal temp”>}

(PRV#5b) Temperature correction for pipe material of Brooks Compact Prover

Using: Ctsp = 1 11 1 2 2e t t e t tb b* * *

Where: Ctsp = Temperature correction factor for steel……….. {Parameter: <“Prv CTS”>} t1 = Average of temperatures at prover valves…….. {Parameter: <“Prv ave prover temp”>} t2 = Prover Invar rod temperature…..……………….. {Parameter: <“Invar rod temp”>} e1 = Area expansion coefficient (ppm/°C)…………… {Parameter: <“Prv sqr expan coeff”>} e2 = Linear expansion coefficient (ppm/°C)…………. {Parameter: <“Prv lin expan coeff”>}

tb = Calibration temperature of prover………...…….. {Parameter: <“Prover cal temp”>}

Calculation PRV#6: Calibrated Volume Pressure Correction (for pipe material)

Using: Cpsp = 1p p * d

E * Wa

Where:

Cpsp = Pressure correction factor for steel………..….... {Parameter: <”Prv CPS”>}

p = Average of pressures at prover valves………… {Parameter: <“Prv ave prover press”>}

pa = Atmospheric pressure (BarA)………………….... {Parameter: <”Atmos pressure”>}

d = Internal diameter of Prover pipe (mm)…………. {Parameter: <“Prv pipe inner dia”>}

E = Modulus of elasticity (N/m²)…………………….. {Parameter: <“Modulus of E”>}

W = Wall thickness of prover pipe (mm)………….…. {Parameter: <“Prv wall thickness”>}


Page 16A.14 7951 2510 (CH16A/CB)

16A.4.2 Volumetric Prover Proving of a Coriolis Mass Meter (by Mass or Volume)

Prove-run calculations for this scenario are listed here for your convenience.

Where appropriate, terms are annotated with the associated software parameters as they are displayed within the 7951 menu system. Unless otherwise stated, these software parameters are to be found in the Prover Archive Session and Run Menus under: <”Proving”>/<”Prover log”>/<”Pipe provers”>.

Calculation: PRV#7: Indicated Meter Mass (Coriolis Meter)

Using: mIM =mKf

N

MC

Where: IMm = Indicated Mass (Coriolis Meter)…………………. {Parameter: <”Prv metered mass”>}

NC = Interpolated Pulse Count (Coriolis Meter)……... {Parameter: <”Prv interp pulses”>}

KfMm = Existing ‘K factor’ of Coriolis Meter (in mass/pulse or pulse/mass units)………….. ………………………………………………..……. {Parameter: <”Prover old K factor”>} *

* Parameter as seen on ‘Metering’ 7951

Calculation: PRV#8: Indicated Meter Volume (Coriolis Meter)

Using: mIV = mmIM

Where: mIV = Indicated Volume (Coriolis Meter)………..…….. {Not in the Menu}

IMm = Indicated Mass (Coriolis Meter)…………………. {See Calculation PRV#7}

m = Fluid density at the Meter…………………..….... {Parameter: <”Meter density”>} *

* Parameter as seen on ‘Metering’ 7951

Calculation: PRV#9: Corrected Prover Volume

Using: pCV = CplpCtlpCpspCtspVB ****

Where: CVp = Corrected Prover Volume (m³)…………….……. {Parameter: <”Prv corr prover vol”>}

VB = Base Volume of Prover (m³)…………………….. {Parameter: <“Prover volume”>}

Ctsp = Temperature correction factor for steel………... {Parameter: <“Prv CTS”>}

Cpsp = Pressure correction factor for steel………….…. {Parameter: <”Prv CPS”>}

Ctlp = Correction factor for effect of temperature on fluid in the Prover…….………….. ……………………………………………….………{Parameter: <”Prv CTLP”>}

Cplp = Correction factor for effect of temperature on fluid in the Prover…….………….. ……………………………………………….………{Parameter: <”Prv CPLP”>}

Calculation: PRV#10: Prover Mass

Using: pCM = BpCV *

Where: CMp = Prover Mass (Kg)………………….…..….……… {Parameter: <”Prover corr mass”>}

CVp = Corrected Prover Volume (m³)……...….….……. {See Calculation PRV#8}

B = Base density…………………..…………..…..….. {Parameter: <”Base density value”>}


7951 2510 (CH16A/CB) Page 16A.15

Calculation: PRV#11: New Meter Factor (for Coriolis Meter)

If proving by Mass….

Using: MFNew = m

pIMCM


CMp = Prover Mass (Kg)…………………..….……… {See Calculation PRV#10}

IMm = Indicated Mass (Coriolis Meter)…………….. { See Calculation PRV#7}

Otherwise…

Using: MFNew = m

pIVCV


CVp = Corrected Prover Volume (m3)……...……… {See Calculation PRV#9}

IVm = Indicated Volume (Coriolis Meter)………….. { See Calculation PRV#8}

Calculation Notes: 1. The new ‘Meter factor’ is always calculated at the end of a successful session. It is then shown in the

session part of the Prover Archive even if it is not offered for acceptance or is offered but then rejected.

2. The ‘Proving’ 7951 (or the combined ‘Metering/Proving’ 7951) will be configured to either offer the new ‘Meter factor’ or offer the new ‘K factor for acceptance to replace an existing meter-run (stream) value.

3. The replaced ‘Meter factor’ value is stored in the Prover Archive menu at the <”Prv old meter factor”> parameter

Calculation PRV#12: New ‘K Factor’

The ‘K factor’ is a result of the liquid flowmeter proving process. This factor is used when calculating the Indicated Volume flow rate at the flow metering point.

Using: KFNew = KF

MFOld

New

Where: KFNew = New calculated ‘K factor’……….……………. {Parameter: <”Prover new K factor”>}

KFOld = Previous calculated ‘K factor’…….…………. {Parameter: <”Prover old K factor”>}

MFNew = New calculated ‘Meter factor’………..…….... {See Calculation PRV#10}

Calculation Notes: 1. The new ‘K factor’ is always calculated at the end of a successful session. It is then shown in the

session part of the Prover Archive even if it is not offered for acceptance or offered but rejected.

2. The ‘Proving’ 7951 (or the combined ‘Metering/Proving’ 7951) will be configured to either offer the new ‘K factor’ or offer the new ‘Meter factor for acceptance to replace an existing metering-run (stream) value.


Page 16A.16 7951 2510 (CH16A/CB)

16A.5 Connections: Inputs and Outputs 16A.5.1 Status Inputs

Power usageRefer to the Status Input example in Chapter 2.

Status Input common pinRefer to the Status Input example in Chapter 2.

Signal pins (Prover and Valves only) Refer to Table 16A.5.1 to find the appropriate functions for your particular set-up.

Table 16A.5.1: Status Inputs for Proving

StatusInput Function D-Type**

Pins Remark

1 Prover detector switch (Start or Stop) SK4/1 2 Prover detector switch (Start or Stop) SK4/2

Read notes G and H

3 (Maintenance-mode request) SK4/3 Read note A4 Strainer indicator (Not Brooks.) SK4/4 Read note J5 Upstream status (Brooks) SK4/5 Read note E6 4-way diverter valve state ‘A’ (Bi. only) SK4/6 Called “Valve 4” in software 7 4-way diverter valve state ‘B’ (Bi. only) SK4/7 Read notes B and F8 Prover outlet valve state ‘A’ SK4/8 Called “Valve 2” in software 9 Prover outlet valve state ‘B’ SK4/9 Read notes B and F

10 Prover inlet valve state ‘A’ SK4/14 Called “Valve 1” in software 11 Prover inlet valve state ‘B’ SK4/15 Read notes B and F12 Stream block valve state ‘A’ SK4/16 Called “Valve 3” in software 13 Stream block valve state ‘B’ SK4/17 Read notes B and F

4-way diverter valve leak detection or14

Nitrogen supply low indicator (Brooks) SK4/18 Read note I

15 Abort / Fault SK4/19 Active = Abort or fault condition

16 Prover in a ‘ready’ state SK4/20 Active = Prover ‘ready’ Inactive = Abort session

IMPORTANT! Status Inputs 8 – 11 relate to the Prover Inlet and Outlet Valves

Notes:

A Some functions can be re-mapped by editing a parameter under <“Configure”>/<”IO physical alloc”>

B ‘Local’ flowmeter proving requires all valve related connections to be made on the flow computer that is performing both stream (metering-run) and proving functions. ‘Remote’ flowmeter proving requires valves connections for a specific stream (metering-run) to be made on the remote flow computer.

C The default signal state of each input is inactive (i.e. logic ‘0’) when using positive logic. Status inputs can be configured for negative logic on an individual basis.

D The prover device must maintain an active signal on Status Input #16 for a prove session to begin and for whole of a prove session.

E Brooks Compact Prover: Indicator is for an ‘up-stream’ signal. The prover device should only keep the indicator inactive while the piston is in the standby (start-up) position and for the duration of a prove-run, including the launch, for a metering-run (stream).

** There are not enough status inputs for proving on a 7951 with klippon type connectors.


7951 2510 (CH16A/CB) Page 16A.17

F Valve status signals are received through paired Status Inputs - nominated as ‘A’ and ‘B’ in tables of pins. Combinations of active and inactive signals are used to differentiate valve states, as guided in Table 16A.5.2 on page 16A.18.

G A ‘Start’ and ‘Stop’ pulse can be received through any of the first two Status Inputs. The 7951 instruments have an automatic detection system that requires no configuring.

H There is a software switch (Parameter) for determining if a detector transmitted pulse is either detected on the positive (rising) edge of a pulse or detected on the negative (falling) edge of a pulse. By default, the positive polarity option is selected.

To make a change to the existing selection:

Navigate to this menu: <"Configure">/<"Prover">/<"Common prv details">. Locate this parameter: <"Prv detect pulse pol">. Edit the selection to be either “Positive polarity" or “Negative polarity”.

I The use of Status Input #14 will depend on the type of Prover selected.

Brooks Compact Prover

The Nitrogen Charge tank can be constantly monitored for a low Nitrogen level. An active signal (assuming positive logic) will be interpreted by the Flow Computer as an indication that a low Nitrogen level of supply exists and will immediately raise an input alarm.

Bi-directional Prover

Leakage from the ‘displacer’ interchange mechanism is checked by monitoring Status Input #14 at key stages during each prove run.

Checks are made by the 7951: Once following the launch of the ‘displacer’ but before it reaches the first detector and then

Continuously (every machine cycle) while the ‘displacer’ travels between detectors. Checking stops as soon as the pulse from the final detector switch is received by the 7951.

An active signal (assuming positive logic) will be interpreted by the 7951 Flow Computer as an indication that a leak exists, and will immediately initiate a controlled end to a prove-run and the prove session.

J Indicator is for a strainer switch input. An active signal indicates the presence of a blockage and will abort a session at the end of a run.

There is a software switch (parameter) for determining if a blocked strainer is either detected by a digital (status) input or by a 4-20mA input. By default, the digital (status) input method is selected, which is not available to a Brooks Compact Prover.

To change over to the 4-20mA (DP) Input method: Navigate to this menu: <"Configure">/<"Inputs">/<"Strainer input"> Work through the parameters as guided in Table 16A.5.1

Table 16A.5.1: Parameters for 4-20mA (DPIT) Strainer Input

Parameters Comments and Instructions

Strainer input src Select the option descriptor containing “mA input” Strainer Ain source Select the analogue input channel used by the device

Strainer DP @ 100% Edit a full-scale DP value Strainer DP @ 0% Edit a value for the lowest DP measurement Strainer DP HI limit ‘Set’ the threshold for detection of a blockage

* Analog Input connection examples can be found in Chapter 2


Page 16A.18 7951 2510 (CH16A/CB)

Table 16A.5.2: Recognised Valve States

‘A’ ‘B’ Valve status Comment

0 0 Failed This indicates the existence of a fault condition

0 1 Close Valve is fully closed

1 0 Open Valve is fully open

1 1 Moving Valve is being re-positioned Key: ‘1’ = Active, ‘0’ = Non-active {Positive logic assumed}


7951 2510 (CH16A/CB) Page 16A.19

16A.5.2 Status Outputs Power usage: Refer to the Status Output connection example in Chapter 2.

Status Input common pin: Refer to the Status Output connection example in Chapter 2.

Signal pins (Prover and Valves only) Refer to Table 16A.5.3, Table 16A.5.4 or Table 16A.5.5.

Table 16A.5.3: Status Outputs for Bi-directional Pipe Prover and Valves Status

Outputs Function D-Type††

Pins Remark

7 Launch displacer (sphere/piston) SK5/6 Active = launched. Read note C8 4-way diverter valve control ‘A’ SK5/7 Called “Valve 4” in software 9 4-way diverter valve control ‘B’ SK5/8 Read notes A and F

10 Prover outlet valve control ‘A’ SK5/14 Called “Valve 2” in software 11 Prover outlet valve control ‘B’ SK5/15 Read notes A and F12 Prover inlet valve control ‘A’ SK5/16 Called “Valve 1” in software 13 Prover inlet valve control ‘B’ SK5/17 Read notes A and F14 Stream block valve control ‘A’ SK5/18 Called “Valve 3” in software 15 Stream block valve control ‘B’ SK5/19 Read notes A and F16 A-B calibrated volume selection SK5/20 6 C-D calibrated volume selection SK5/5

Read note D

Table 16A.5.4: Status Outputs for Unidirectional Pipe Prover and Valves Status

Outputs Function D-type pins Remark

7 Launch ‘displacer’ (sphere/piston) SK5/6 Active = launched. Read note C8 Proving session in progress SK5/7 Inactive = No prove session

10 Prover outlet valve control (A) SK5/14 Called “Valve 2” in software 11 Prover outlet valve control (B) SK5/15 Read notes A and F12 Prover inlet valve control (A) SK5/16 Called “Valve 1” in software 13 Prover inlet valve control (B) SK5/17 Read notes A and F14 Stream block valve control (A) SK5/18 Called “Valve 3” in software 15 Stream block valve control (B) SK5/19 Read notes A and F

Table 16A.5.5: Status Outputs for Brooks Compact Pipe Prover and Valves Status

Outputs Function D-type pins Remark

6 Plenum pressure charge SK5/5 Active = ‘Charge’ command 7 Launch displacer (piston) SK5/6 Active = launched. Read note C8 Start hydraulic pump SK5/7 Active = Retract piston to standby 9 Stop hydraulic pump SK5/8 Active = Stop (piston retracted) 10 Prover Outlet valve control ‘A’ SK5/14 Called “Valve 2” in software 11 Prover Outlet valve control ‘B’ SK5/15 Read notes A and F12 Prover Inlet valve control ‘A’ SK5/16 Called “Valve 1” in software 13 Prover Inlet valve control ‘B’ SK5/17 Read notes A and F14 Stream Block valve control ‘A’ SK5/18 Called “Valve 3” in software 15 Stream Block valve control ‘B’ SK5/19 Read notes A and F16 Open the Plenum pressure vent Active = ‘Vent’ command

†† There are not enough status outputs on a 7951 with klippon type connectors.


Page 16A.20 7951 2510 (CH16A/CB)

Notes:

A ‘Local’ flowmeter proving requires all valve related connections to be made on the 7951 that is performing both stream (metering-run) and proving functions.

‘Remote’ flowmeter proving requires valves connections to be made on the remote flow computer.

B The default signal state of each output is inactive (i.e. logic ‘0’) when using positive logic. Status outputs can be configured for negative logic on an individual basis

C Status Output #7 is kept active for the whole of the initialisation phase of a proving session and kept active for the whole of a prove-run. It is inactive between prove-runs.

D Plenum pressure can be either increased or decreased by activating Status Outputs #6 (to increase) and #16 (to reduce). During the stabilisation phase, the 7951 instrument monitors plenum pressure from a mA Input and automatically uses these status outputs to achieve a user-defined level

E Calibrated volume selection is signalled to the prover through paired Status Outputs #6 and #16. The combination of active and inactive outputs tell the prover device which calibrated volume should be used for a prove session. See Table 16A.5.6 for the status output logic.

F Valve command signals are transmitted through paired Status Outputs. Pairs are nominated as ‘A’ and ‘B’ in tables of pins. Combinations of active and inactive signals are used to differentiate valve commands, as guided in Table 16A.5.7.

Table 16A.5.6: Calibrated Volume Selection

‘A’ ‘B’ Volume selected Comment

0 0 BD Calibrated volume between detector switch ‘B’ and ‘D’ 0 1 BC Calibrated volume between detector switch ‘B’ and ‘C’ 1 0 AD Calibrated volume between detector switch ‘A’ and ‘D’ 1 1 AC Calibrated volume between detector switch ‘A’ and ‘C’

Table 16A.5.7: Valve Commands

‘A’ ‘B’ Valve

Command Comment

0 0 Idle Valve remains at present position 0 1 Close Fully close valve 1 0 Open Fully open valve 1 1 (Not used) Never issued from the 7951.

Key: ‘1’ = Active, ‘0’ = Non-active {Positive logic assumed}


7951 2510 (CH16A/CB) Page 16A.21

16A.5.3 Analog Inputs

Several metering (stream) measurements are used in the prover calculations that are performed on the ‘Proving’ flow computer:

Temperature (at the Prover Inlet valve) *…………........… All Provers. Pressure (at the Prover Inlet valve) *...........…………...… All Provers. Temperature (at the Prover Outlet valve) *………………. Bi-directional piper prover only. Pressure (at the Prover Outlet valve) *.…………….…….. Bi-directional piper prover only. Brooks Plenum Pressure.................…………...………..... Brooks Compact Prover only.

* When there is just one sensor at a valve, you must use that sensor input for both the outlet and inlet measurements.

The ‘Live’ measurements are either: Directly input to the combined ‘Proving’ and ‘Metering’ flow computer (for ‘local’ proving), or Directly input to the ‘Metering’ Flow Computer and then transmitted to the ‘Proving’ flow computer.

Analog inputs on the 7951 flow computer are not dedicated to a specific measurement. Connect each sensor to an unused analog input, as guided in Chapter 2, and then configure that analog input and measurement task by using an appropriate Wizard (Chapter 10), and fine-tune set-up using Chapter 11.

16A.5.4 Pulse (Turbine) Inputs

A guide to connecting a supported volumetric/mass flowmeter to the 7951 is in Chapter 2. Configure using an appropriate Wizard (Chapter 10), and fine-tune set-up using Chapter 11.

16A.5.5 ‘Remote’ Proving Connection Summary Summary of 7951 flow computer connections as required for ‘remote’ proving:

‘Prover’ Flow Computer ‘Metering’ Flow Computer

Status Inputs for Prover outputs Status Inputs for valve monitoring

Status Outputs for Prover inputs Status Outputs for valve control

Pulse inputs for flowmeter output Pulse inputs for flowmeter output

Port for MODBUS communications with ‘Metering’ Flow Computer

Port for MODBUS communications with ‘Prover’ Flow Computer


Page 16A.22 7951 2510 (CH16A/CB)

16A.6 Valve Control and Monitoring This section explains how the 7951 can position valves to allow flow into a ‘Prover-loop’, and then return them to a position for normal flow. Configuration task details for valves are also provided.

16A.6.1 Overview

Valves can be controlled and monitored either by:

A 7951 performing both ‘Proving’ and ‘Metering’ functions (i.e. ‘local’ proving), or A 7951 performing mostly ‘Proving’ functions but instructing a second 7951 to do the valve controlling.

Valve states are received by the ‘Metering’ 7951 and passed back to the ‘Proving’ 7951.

In both cases, valves can be controlled automatically, manually or a mixture of the two.

16A.6.2 Fully Automatic Valve Control and Monitoring The metering-run Block valve, Prover Isolation valve and Prover outlet valve are all connected to a 7951 by means of Status Inputs and Outputs.

Stream MeterProver Inlet

Stream block

Prover outlet

Flow direction

To Prover From Prover

The 7951 allocates two Status Inputs and two Status Outputs to each valve. Status Inputs are used to monitor the state of each valve. Combinations active or inactive signals from paired inputs are interpreted to obtain a valve state. (See “valve states” for details). Status Outputs are used to command each valve to re-position and, therefore, alter the flow path. Commands are in the form of a combination of active or inactive pulsed-outputs. (See “valve commands format” for details). At the start of a prove session, flow is re-directed into a Prover-loop by opening both Prover valves and then closing the Metering-run Block valve. After a prove session is completed flow is stopped from entering the Prover-loop by opening the Steam Block valve and closing both Prover valves. The diagram below shows these sequences.

Open prover outlet valve

Open prover inlet valve

Close stream block valve

Timeout

Timeout

Timeout

Valves aligned Valve failure

Open stream block valve

Close prover inlet valve

Close prover outlet valve

Timeout

Timeout

Timeout

Valves returned Valve failure

VALVE ALIGNMENT VALVE RETURN

Valve positioned

Valve positioned

Valve positioned

Valve positioned

Valve positioned

Valve positioned

Both sequences in a prove-run are fixed but the time between issuing commands can be user-defined. Valves also have a user-defined amount of time to respond to commands. Valve time-outs always cause a prove-run to be aborted.

Note: Valves must be in the correct initial position prior to starting a prove session – the block valve for the flowing stream must be open and the divert valve must be closed. Failure to observe this will result in a “Prover Abort Init i” alarm.


7951 2510 (CH16A/CB) Page 16A.23

16A.6.3 Fully Manual Valve Control and Monitoring

There are no physical connections to valves, and valve time-outs are switched off.

Prior to a prove session, valves must be re-positioned using another (off-line) system to direct flow into the prover-loop. After starting a prove session, the operator then simply follows on-screen prompts to answers ‘yes’ (or ‘no’) to confirm to the 7951 that a valve has been opened or closed by some other means. Pressing ‘no’ always aborts a prove session.

At the close of a prove session, valves should be returned to their original positions using another (off-line) system and the operator, again, simply follows on-screen prompts to answers ‘yes’ (or ‘no’) to confirm the state of each valve.

The valve ‘alignment’ and ‘return’ sequences are identical to the automatic process.

16A.6.4 Mixture of Automatic/Manual Valve Control and Monitoring

It is also possible to have some valves under automatic control the remainder under manual control. This is determined during the configuration task as detailed in Section 16A.6.7

Warning! There are data locations within the <“Valves”> menu to: (a) Manually issue commands to a valve (See notes), (b) Monitor commands being issued by automatic control (during a prove). and (c) Monitor valve states. Notes: 1. Operators can select, at their leisure, a ‘valve command’ for any one of four

connected valves in any order. This can be done either at the front panel keyboard or over a serial communications (MODBUS network) link. Manual commands are transmitted, as pulses, by the 7951 to valve controllers when the operator selects a valve command.

2. Do not issue commands to valves in this way unless it is absolutely necessary. However, monitoring these locations can be useful.

16A.6.5 Valve Command Formats

Commands are transmitted through a paired status outputs (nominated ‘A’ and ‘B’). Combinations of a active (logic ‘high’) or inactive (‘low’) signals are issued simultaneously on each output to differentiate commands. Table 16A.6.1 shows the valve commands that should be recognised by a valve controller.

Table 16A.6.1: Status output logic for valve commands

‘A’ ‘B’ Valve Command Command Use

0 0 Idle Valve remains at present position

0 1 Close Fully close valve or Rotate 4-way diverter valve to the reverse position

1 0 Open Fully open valve or Rotate 4-way diverter valve to the forward position

1 1 (Not used) Never issued by the 7951.

(Positive Logic by Default)

Note: Only Bi-directional ‘prover-loops’ feature a 4-way diverter valve


Page 16A.24 7951 2510 (CH16A/CB)

Two valve command signalling methods are supported: Pulse mode and Level mode.

1. Open/close valve commands with the “pulse” drive method

Paired status outputs issue a combination of two short pulsed (active) signals to the valve (controller). The 7951regards the valve as being fully opened or closed when the valve state is interpreted as “open” (or “closed”).

Valve"Open"

command

Status output (A)

Status output (B)

Status input (A)

Status input (B)

valve response timeout

userdefinedduration

Valve "opened" state

Figure 16.5: Successful closure of a valve (“pulse” drive method)

2. Open/close valve commands with the “level” drive method

Paired status outputs issue a combination of two pulsed signals to the valve (or, most likely, a valve controller). Signal levels are normally sustained until the valve state is interpreted by the 7951 as “open” (or “closed”).

Valve "open" command

Status output (A)

Status output (B)

Status input (A)

Status input (B)

Valve "opened" state

valve response timeout

Figure 16.6: Successful closure of a valve (“level” drive method)


7951 2510 (CH16A/CB) Page 16A.25

16A.6.6 Valve States

Paired status inputs are monitored to check the result of an issued command. Valve states are transmitted through paired status inputs (nominated ‘A’ and ‘B’). Combinations of a active (logical ‘high’) or inactive (logical ‘low’) signal are received simultaneously on each input to differentiate the different states.

Table 16A.6.2 shows all the valve states that should be communicated by a valve controller:

Table 16A.6.2: Status input logic for valve states

‘A’ ‘B’ Valve status (as displayed) Comment

0 0 Failed This indicates a fault condition

0 1 Close Valve is fully closed

1 0 Open Valve is fully open

1 1 Moving Valve is being re-positioned

Note: No configuration work is required for this feature if using default positive logic

16A.6.7 Configuration Details (for the ‘Proving’ 7951 and ‘Metering’ 7951)1. Navigate to this menu: <“Configure”>/<“Valves”>

The expression <“Configure”>/<“Valves”> translates into the following keyboard sequences: (1) Press the MAIN-MENU Button (2) Use the DOWN-ARROW button to scroll through several pages. Halt when “Configure”

appears. (3) Press the lettered-button that is alongside that description. (4) Use the DOWN-ARROW button to scroll through several pages. Halt when the description

“Valves” appears. (5) Press the lettered-button that is alongside that description.

2. Work through this Parameter list for each valve

Parameters Instructions and Comments

Valve drive mode Choose between “Pulse” drive mode and “Level” drive mode.

Valve duration Enter a value for how long a pulse (of a valve command) is to be sustained. Default time is 0 (machine cycles).

Valve timeout Enter the period allowed for the valve to be re-positioned. Use 0 seconds when using manual valve control. Default time is 0 (machine cycles).

Valve control Choose between “Automatic” control or “Manual” control.

Note: Valves designations are listed in Section 16A.5.

3. Navigate to this menu: <“Configure”>/<“Prover”>

4. Locate this parameter: <“Prv auto rtn valves”>

5. Select “Yes” or “No”:

“Yes” The 7951 is fully responsible for managing the return of (supported) valves to their original pre-prove positions at the end of a prove session. No interaction is required.

“No” Valves are re-positioned by another (off-line) system at the end of a prove session. On-screen prompts will appear for an operator to confirm that valves are in their original pre-prove positions.

(Ignore steps 6 and 7 if relying on automatic valve control and monitoring)


Page 16A.26 7951 2510 (CH16A/CB)

6. Locate this parameter: <“Prv valve confirm”>

7. Select a mode for confirming the position of valves

“Ignore” 7951 relies on valve state feedback through paired status outputs. “Grouped” 7951 prompts for a single button-press to confirm that all valves are in position. “Individually” 7951 prompts for a single button-press to confirm that a particular valve is in position.

You can now proceed to the next section to continue the configuration.


7951 2510 (CH16A/CB) Page 16A.27

16A.7 Configuration Tasks: Proving Details This section explains how to configure basic details about the prover device and how a proving session should operate. There are separate communication set-up tasks for ‘local’ proving and ‘remote’ proving. Use Table 16A.7.1 to identify the appropriate configuration tasks

Mini-Index16A.7.1 Configuration Task #1: Metering-run Measurement Functions……..….…..……….. 16A.28

16A.7.2 Configuration Task #2: Common Prover details……………………………………… 16A.31

16A.7.3 Configuration Task #3a: Bi-directional /Unidirectional Prover details……………… 16A.35

16A.7.4 Configuration task #3b: Brooks Compact Prover details………………………..…… 16A.36

16A.7.5 Configuration task #4a: Serial Port Communications (‘local’ prove………………… 16A.38

16A.7.6 Configuration task #4b: Serial Port Communications (‘remote’ prove)…………….. 16A.39

Table 16A.7.1: Configuration tasks required for each prover

Prover Type Local/RemoteProving

Configuration Tasks

Unidirectional Local 1 2 3a 4a

Unidirectional Remote 1 2 3a 4b

Bi-directional Local 1 2 3a 4a

Bi-directional Remote 1 2 3a 4b

Brooks Compact Local 1 2 3b 4a

Brooks Compact Remote 1 2 3b 4b

“Local” = Combined ‘Metering/Proving’ 7951 “Remote” = Separate ‘Metering’ 7951 and ‘Proving’ 7951


Page 16A.28 7951 2510 (CH16A/CB)

16A.7.1 Configuration Task #1: Metering-run Measurement Functions (Unless indicated, this task is to be attempted on the 7951 performing the ‘Metering’ functions).


1. Ensure that the Metering-run measurement tasks are configured

Measurement task Parameterss to check Which 7951?

Flowmeter details Various – See Chapter 11 Proving and Metering

Flow rates Various – See Chapter 11 Metering

Metering-run density Meter density Metering

Base density Base density value Metering

Metering-run temperature Meter temperature Metering

Metering-run pressure Meter pressure Metering

Note: Refer to Chapters 3, 10 and 11 for details of these measurements

2. Set-up Plenum Pressure Monitoring and Control (Brooks Compact Prover only)

Objectives: Review the Plenum pressure control set-up Receive Plenum pressure measurements from a field transmitter. Establish the target level of Plenum pressure needed for a proving session to begin. Define dead-band limits for controlling and maintaining Plenum pressure. Define limits for checking that Plenum pressure is sufficient before and during each run.

What to do:(2a) Review Plenum Pressure Control set-up

Ensure that Status Outputs #6 and #16 are physically connected to the correct inputs on the Brooks Compact Prover. Refer to the Section 16A.5.2 (on page 16A.19) if this has not been established.

(2b) Ensure that one Analogue Input or HART/Analogue Input is wired and configured to receive Plenum Pressure measurements.

If using HART… Use Chapter 17 to set-up HART Inputs and then continue with step 2c

If using mA… Use Chapter 2 for wiring information, Chapter 11 for mA Input configuration details and then continue with step 2c

(2c) Navigate to: <“Configure”>/<“Pressure”>/<”Prover pressure”>/<”Prv plenum pressure”>

(2d) Work through Parameter List 16A.7.1

Parameter List 16A.7.1: Plenum pressure measurement parameters

Parameter * (as displayed) Instructions and Comments

Plenum press 100% ‘SET’ a value for the highest measurement supported by the transmitter

Plenum press 0% ‘SET’ a value for the lowest measurement supported by the transmitter

Plenum press source Change the selection to the option name that corresponds to the mA-type Analogue Input or HART Input

Plenum press value Change the status to be “Live”

* Abbreviation used: “Press” = Pressure


7951 2510 (CH16A/CB) Page 16A.29

(Step 2 continued …)

(2e) Navigate to this menu: <“Configure”>/<“Prover”>/<“Brooks compact”> (2f) Work through Table 16A.7.2.

Table 16A.7.2: Brooks Compact Prover Device Parameters


Prv plenum press tmo ‘SET’ the length of time allowed for Plenum pressure to be stabilised within the control limits and/or alarm limits. A session is aborted if Plenum pressure is outside these limits when this time-limit expires.

Prv plenum const R ‘SET’ a value for the Nitrogen spring pressure constant ‘R’ if the Plenum pressure target is to be calculated.

Plenum press target ‘SET’ a value or change the state to “Live” for the 7951 to calculate a target value. Calculation = (<”Meter pressure”> / <”Prv plenum const R“>)

Plenum P ctrl LO lmt ‘SET’ the lower limit - a negative value - to be used when establishing a sufficient level of Plenum pressure for a session. ‘Charge’ and ‘Vent’ controls (Status Outputs) are automatically used by the Flow Computer to attain a target level. The limit is expressed as a percentage below the target level.

Plenum P ctrl HI lmt ‘SET’ the upper limit value - a positive value - to be used when establishing a sufficient level of Plenum pressure for a session. ‘Charge’ and ‘Vent’ controls (Status Outputs) are automatically used by the Flow Computer to attain a target level. The limit is expressed as a percentage above the target level.

Plenum P alm LO lmt ‘SET’ a limit value - a negative value - for raising an alarm when the Plenum pressure is a percentage below the target level. The alarm has no effect during a prove run but the Flow Computer will delay the next prove run until back within limits.

Plenum P alm HI lmt ‘SET’ a limit value - a positive value - for raising an alarm when the Plenum pressure is a percentage above the target level. The alarm has no effect during a prove run but the Flow Computer will delay the next prove run until back within limits.

3. Prover Inlet and Outlet Temperature

Objectives: Get scaled temperature measurement values.

What to do:(3a) Navigate to this menu: <“Configure”>/<“Temperature”>/<“Prover temp”>

(3b) Work through this Parameter list:


Inlet temp @ 100% ‘SET’ a value for the maximum temperature that is supported by the transmitter. THIS IS NOT APPLICBLE IF USING HART.

Inlet temp @ 0% ‘SET’ a value for the minimum temperature that is supported by the transmitter. THIS IS NOT APPLICBLE IF USING HART.

Inlet temp source Edit the selection to be the description that corresponds to the input used by the sensor. (See 16A.5.3 on page 16A.21 for connection information)


Page 16A.30 7951 2510 (CH16A/CB)

(Step 3c continued…)

Inlet temp LO lmt ‘SET’ a lower limit for the scaled inlet temperature value. An alarm will be raised when this lower limit is exceeded.

Inlet temp HI lmt ‘SET’ a higher limit for the scaled inlet temperature value. An alarm will be raised when this higher limit is exceeded.

Inlet temp FB type (Optional) Select a fallback function - “Last good value” or “Fallback value” - for when the transmitter can not provide a live value.

Inlet temp FB val (Optional) ‘SET’ a value for the “Fallback value” function (if it is selected).

Inlet temp offset (Optional) Use this for on-line calibration of the transmitter

Prover inlet temp Change the status to be “Live”.

Outlet temp @ 100% ‘SET’ a value for the maximum temperature that is supported by the transmitter. THIS IS NOT APPLICBLE IF USING HART.

Outlet temp @ 0% ‘SET’ a value for the minimum temperature that is supported by the transmitter. THIS IS NOT APPLICBLE IF USING HART.

Outlet temp src Edit the selection to be the description that corresponds to the input used by the sensor.

Outlet temp LO lmt ‘SET’ a low limit for the scaled outlet temperature value. An alarm will be raised when this lower limit is exceeded.

Outlet temp HI lmt ‘SET’ a high limit for the scaled outlet temperature value. An alarm will be raised when this higher limit is exceeded.

Outlet temp FB type (Optional) Select a fallback function - “Last good value” or “Fallback value” - for when the transmitter can not provide a live value.

Outlet temp FB val (Optional) ‘SET’ a value for the “Fallback value” function (if it is selected).

Outlet temp offset (Optional) Use this for on-line calibration of the transmitter.

Prover outlet temp Change the status to be “Live”.

(End of configuration task #1)


7951 2510 (CH16A/CB) Page 16A.31

16A.7.2 Configuration Task #2: Common Prover details (Unless indicated, this task is to be attempted on the 7951 performing the ‘Proving’ functions).

Objectives: Identify the type of Prover. Nominate whether to prove by volume or by mass. Various flowmeter proving scenarios are

supported, as illustrated by the proving calculations shown in Section 16A.4 (on page 16A.11) Provide fundamental information about that Prover. Set limits for the ‘Meter Factor’ validation process and the Prover-loop stabilisation checks. Set time-outs for the various proving events. Provide optional information for the printable Prover report.

What to do:Follow these instructions:

1. Navigate to this menu: <“Configure”>/<“Prover”>/<”Common prv details”>

2. Work through this Parameter list… (Some menu searching is required)


Prover type Identify the type of Prover (and the calibration volume). Note: The Bi-directional option texts all have a two lettered code. These letters determine the base (calibrated) volume to be used. For example, “BD” is the base (calibrated) volume between detector switch ‘B’ and detector switch ‘D’.

Prove by Vol Mass Nominate whether to prove by volume or by mass. See Section 16A.4 (on page 16A.11) if you information on flowmeter proving scenarios.

Prv IO assign Identify the type of Prover. This action selects a specific valve control and monitoring scheme.

Prv pipe inner dia ‘SET’ a value for the inner diameter of the ‘Prover-loop’ pipe, unless using the Brooks Compact Prover.

Selecting a Brooks Compact Prover will trigger the copying of a value from a built-in look-up table.

Prv wall thickness ‘SET’ a value for the thickness of the ‘Prover-loop’ pipe, unless using the Brooks Compact Prover. Selecting a Brooks Compact Prover will trigger the copying of a value from a built-in look-up table.

Modulus of E ‘SET’ a value for the modulus of elasticity.

Prover cal temp ‘SET’ a value for the temperature at which the Prover was calibrated.

Site name (Optional) Edit a site name to be included in the Prover Report.

Meter serial number (Optional) Edit a text label to be included in the Prover Report.

Meter number (Optional) Edit a text label to be included in the Prover Report.

3. Navigate to this menu: <“Configure”>/<“Prover”>/<”Common prv operatn”>

4. Work through this Parameter list… (Some menu searching is required)


Prv operation Select the form of interaction between the operator and the ‘Proving’ 7951

Prv calc select Select whether to calculate a new ‘Meter Factor’ or a new ‘K Factor’

Prover max runs Select the total number of prove-runs for a prove session

Prover req good runs Select the number of consecutive good (passed) prove-runs required for a successful proving session. (Read note ‘A’)


Page 16A.32 7951 2510 (CH16A/CB)

(Step 4 continued…)

Prv meter factor dev ‘SET’ an upper limit (%) for the deviation of calculated factor values

This limit check and the deviation calculation is performed as the first part of the ‘Meter Factor’ validation process. (Read note ‘A’)

The 7951 deviation calculation involves the highest and lowest factor values. (Read note ‘B’)

Exceeding the limit does not raise an alarm but a new attempt is made to get consecutive good (passed) prove-runs from the remaining session.

Note: A zero value does not switch off this limit check.

Prv meter factor LO ‘SET’ a lower limit for the average of factor values from a completed sequence of consecutive good (passed) prove-runs.

This limit check is performed as the second part of the ‘Meter Factor’ validation process but only if the deviation index is sufficient.

Read notes ‘B’ and ‘C’

Prv meter factor HI ‘SET’ an upper limit for the average of factor values from a completed sequence of consecutive good (passed) prove-runs.

This limit check is performed as the second part of the ‘Meter Factor’ validation but only if the deviation index is sufficient.

Read notes ‘B’ and ‘C’

Prv interp pulse dev ‘SET’ an upper limit (%) for the deviation of the pulse counts from a completed sequence of consecutive good prove-runs.

This limit check and the deviation calculation is performed as the final part of the ‘Meter Factor’ validation process but only if previous checks did not fail. (Read note ‘A’)

The 7951 deviation calculation involves the highest and lowest pulse counts. (Read note ‘D’)

Exceeding the limit does not raise an alarm but a new attempt is made to get consecutive good (passed) prove-runs from the remaining session.

Note: A zero value does not switch off this limit check.

Prover start delay ‘SET’ a value for the maximum amount of time allowed for the ‘displacer’ to reach the ‘start’ detector switch.

Note: A zero value represents 0 seconds.

Prover start timeout ‘SET’ a value for the maximum amount of time allowed for the period between: (a) the 4-way diverter valve being in the correct position and(b) the ‘displacer’ (sphere or piston) being launched.


THIS PARAMETER IS FOR A BI-DIRECTIONAL PROVER.

Prover run timeout ‘SET’ a value for the maximum amount of time allowed for the period between: (a) the displacer reaching the ‘start’ detector switch and(b) the displacer reaching the ‘end’ detector switch.


Prv inter-run delay ‘SET’ a value for the maximum allowed time between each prove-run.


Prover end delay ‘SET’ a value for the maximum allowed time for the period between: (a) the ‘displacer’ reaching the ‘end’ detector switch and(b) the ‘displacer’ reaching the end of the Prover-loop.



7951 2510 (CH16A/CB) Page 16A.33


Prv temperature diff ‘SET’ a limit for the maximum allowed difference between the temperature at the flow metering point and the averaged temperatures at the Prover Inlet and Outlet valves. (Read note ‘F’).

Prv pressure diff ‘SET’ a limit for the maximum allowed difference between the pressure at the flow metering point and the averaged pressures at the Prover Inlet and Outlet valves. (Read note ‘F’).

Prv flow rate diff ‘SET’ a value for:

(a) The maximum allowed difference between two consecutive metering-run Indicated Volume flow rate measurements. (Read note ‘E’).

(b) The maximum allowed difference between the metering-run Indicated Volume rate and the Prover volume rate during a machine cycle. (Read notes‘F’ and ‘G’)

Prv stable timeout ‘SET’ a period for the prover-loop to stabilise.

Prv stable temp diff ‘SET’ a value for the maximum allowed difference between the temperature at the flow metering point and the averaged temperatures at the Prover Inlet and Outlet valves. (Read note ‘E’).

Prv stable press diff ‘SET’ a value for the maximum allowed difference between the pressure at the flow metering point and the averaged pressures at the Prover Inlet and Outlet valves. (Read note ‘E’).

Prv stable flow diff ‘SET’ a value for the maximum allowed difference between the rate of flow at the metering-point and the rate of flow in the prover-loop. (Read note ‘E’).

Notes: A ‘Meter Factor’ validity checks occur when there is a completed sequence of consecutive good (passed)

prove-runs as determined by <”Prover req good runs”>. A session is automatically finished when all validation checks are successful.

B A ‘Meter Factor’ deviation calculation is performed during a ‘Meter Factor’ validity check.

Using: MFR =MF MF

MFHigh Low

Ave*100

Where: MFR = Deviation index (%)…………....……………….. {Parameter: <”Prv MF deviation”>} *

MFHigh = Highest ‘Meter Factor’ from all good prove-runs in the session so far.

MFLow = Lowest ‘Meter Factor’ from all good prove-runs in the session so far.

And: MFAve =MF MFHigh Low

2

* Located within the menu <”Proving”>/<”Prover log”>

C Exceeding this limit does not raise an alarm but a new attempt is made to get a complete sequence of consecutive good (passed) prove-runs from the remaining session.


Page 16A.34 7951 2510 (CH16A/CB)

D A pulse count deviation calculation is performed during a ‘Meter Factor’ validity check.

Using: NCR =NC NC

NCHigh Low

Ave*100

Where: NCR = Pulse count deviation (%)………………...….... {Parameter: <”Prv interp pulse dev”>}

NCHigh = Highest pulse count from all good prove-runs in the session so far.

NCLow = Lowest pulse count from all good prove-runs in the session so far.

And: NCAve =NC NCHigh Low

2

E This limit is checked every machine cycle during the stabilisation phase. Exceeding the limit will not raise an alarm but it will, if stability is not already achieved, trigger a new attempt to detect stability for 10 consecutive cycles during the remainder of the phase.

F This limit is checked once after a prove-run is completed. Exceeding the limit will raise an alarm and record the prove-run as a failure. A new attempt is made to get the required number of consecutive good (passed) prove-runs from the remainder of the session.

G The Prover Volume flow rate is calculated following the completion of a prove-run. It is used for a percentage-based comparison with the metering-run Indicated Volume flow rate.

Using: CVRP =CV

tP * 3600

Where: CVRP = Corrected Volume flow rate in prover-loop (in m3/hour)………… {Not in the menu}

CVP = Corrected Calibrated Prover Volume (in m3)

t = Duration of prove-run (in seconds)…………………………………{Not in the menu}


7951 2510 (CH16A/CB) Page 16A.35

16A.7.3 Configuration Task #3a: Bi-directional /Unidirectional Prover details (Unless indicated, this task is to be attempted on the 7951 performing the ‘Proving’ functions).

Follow these instructions: 1. Navigate to this menu: <“Configure”>/<“Prover”>/<”Uni/bi pipe prover”>

The expression <“Configure”>/<“Prover”> translates into the following keyboard sequences: (1) Press the MAIN-MENU Button (2) Use the DOWN-ARROW button to scroll through several pages. Halt when “Configure”

appears. (3) Press the lettered-button that is alongside that description. (4) Use the DOWN-ARROW button to scroll through several pages. Halt when the description

“Prover” appears. (5) Press the lettered-button that is alongside that description.

2. Work through this parameter list:


Prover volume uni/AC ‘SET’ a value for the precise base (calibrated) volume of liquid between detector switch ‘A’ and detector switch ‘C’.

Prover volume AD ‘SET’ a value for the precise base (calibrated) volume of liquid between detector switch ‘A’ and detector switch ‘D’. THIS IS NOT APPLICABLE TO A UNIDIRECTIONAL PROVER.

Prover volume BC ‘SET’ a value for the precise base (calibrated) volume of liquid between detector switch ‘B’ and detector switch ‘C’. THIS IS NOT APPLICABLE TO A UNIDIRECTIONAL PROVER.

Prover volume BD ‘SET’ a value for the precise base (calibrated) volume of liquid between detector switch ‘B’ and detector switch ‘D’. THIS IS NOT APPLICABLE TO A UNIDIRECTIONAL PROVER.

Prv metered volume This shows the base (calibrated) volume that the displacer will travel through.

Values are copied from the entered volume data. The selection of the value to copy is determined from the setting for <“Prover type”>.

Prv expansion coeff ‘SET’ a value for the Prover Expansion Coefficient. (See Section 0 on page 16A.12 for use in 7951 calculations)

(End of configuration task #3a)


Page 16A.36 7951 2510 (CH16A/CB)

16A.7.4 Configuration task #3b: Brooks Compact Prover details (This task is to be attempted on the 7951 instrument that is performing the ‘Proving’ functions).


1. Navigate to the menu: <“Configure”>/<“Prover”>/<”Brooks compact”>



Brooks size Selecting a size will trigger the copying of default values from a look-up table to various parameters. (See Table 16A.7.2 below)

Parameters affected, unless using “Other” size option:

1. <”Prv plenum const R”> 2. <”Prv upstream multipl”> 3. <”Prv wall thickness”> 4. <”Prv pipe inner dia”>……………………. (Flow tube ID (inches))

Note:It is necessary to ‘SET’ values for these parameters if using the “Other”size option.

Prover tube material Selecting a material option will trigger the copying of default values from a look-up table to several parameters. (See Table 16A.7.3 below )

Parameters affected, unless using “Other” material option:

1. <”Modulus of E”>…………………………………(Modulus of elasticity) 2. <”Prv sqr expan coeff”>….…(Square coefficient of expansion per F)

Note:It is necessary to ‘SET’ values for these parameters if using the “Other”material option.

Prv lin expan coeff ‘SET’ a value for the linear expansion coefficient.

Table 16A.7.2: Brooks Compact Prover (Sizes)

Brooks size Plenum Press. Constant ‘R’

Up-stream Multiplier

Flow tube ID (inches)

Wall thickness (inches)

8 inch 3.5 0.990590 8.250 0.6875

12 inch mini 3.2 0.991670 12.250 0.8750

12 inch std 3.2 0.991670 12.250 0.8750

18 inch 5.0 0.993010 17.500 1.250

24 inch 5.88 0.993464 25.500 1.0625

40 inch 4.45 0.985938 40.000 1.500

Other User-defined User-defined User-defined User-defined

Table 16A.7.3: Brooks Compact Prover (Tube Material)

Tube material Modulus of Elasticity Per p.s.i.

Square coefficient of expansion per F

304 st steel 28,000,000 0.0000177

17-4 st steel 28,500,000 0.0000120

Carbon steel 30,000,000 0.0000124

Other User-defined User-defined


7951 2510 (CH16A/CB) Page 16A.37


Brooks vol downstrm ‘SET’ a value for the Base Volume down-stream of the Prover.

Brooks vol upstream Either ‘SET’ a value or change the status to “Live” to get the Base Volume calculated by the 7951

The calculation is ( <”Prv upstream multipl”> * <”Brooks vol downstream”>)

Prover volume The value displayed will depend on the selection made for the position of the (turbine) flowmeter.

Up-stream: Value is copied from <”Brooks vol upstream”>

Down-stream: Value is copied from <”Brooks vol downstream”>

Flow meter position Selecting the position will affect the value displayed by <”Prv metered volume”>

Prv passes per run Select the number of volume sweeps (passes of the piston) that are required for a full prove-run.

Prv start pump tmo (Prover Start Pump Time-out)

‘SET’ a value for the maximum time that Status Output #8 should be active. This allows time for the Prover to respond to ‘Start Hydraulic Pump’ Status Output signal.

Prv stop pump tmo (Prover Stop Pump Time-out) ‘SET’ a value for the maximum time that Status Output #9 should be active. This allows time for the Prover to respond to the ‘Stop Hydraulic Pump’ Status Output signal.

Invar rod temp ‘SET’ a value for the Invar rod temperature. This value is normally the ambient temperature of the environment.

(End of configuration task #3b)


Page 16A.38 7951 2510 (CH16A/CB)

16A.7.5 Configuration task #4a: Serial Port Communications (‘local’ prove) Objective: Set-up for a combined ‘Metering’ and ‘Proving’ Flow Computer.


1. Navigate to this menu: <“Configure”>/<“Other parameters”>/<“Communications”>/<“MODBUS master”>/<”Slave devices”>



Slave device 1 func Edit the option descriptor to be “FC PROVER”.

Slv device 1 address ‘SET’ the value to 0 (for ‘remote’ proving).

3. Navigate to the menu: <“Proving”>/<“Device to prove”>.

4. Find the parameter with this description: <“Proving device”>.

5. Edit the option to be “Device 1”.

(End of Configuration Task #4a)


7951 2510 (CH16A/CB) Page 16A.39

16A.7.6 Configuration task #4b: Serial Port Communications (‘remote’ prove) Objectives:The ‘Proving’ 7951 (performing mostly proving functions) should be set-up as a ‘Master’ on a MODBUS network. Other devices, such as the ‘Metering’ 7951‡‡ (performing mostly metering functions), must be set-up as a ‘slave’ on a MODBUS network. This organisation allows:

1. Metering data to be transmitted to the ‘Proving’ 7951 for use in proving calculations, 2. A new meter factor to be forwarded to the ‘Metering’ 7951, 3. The ‘Proving’ 7951 to ask the ‘Metering’ 7951 to control valves. and 4. The ‘Metering’ 7951 to forward valve states to the ‘Proving’ 7951.

To avoid repetition, the following instructions are written with the assumption that the ‘Metering’ Flow Computer is being set-up as slave with MODBUS address of 1.


(Steps 1 to 5 are for the ‘Proving’ 7951 Flow Computer)

1. Ensure that the serial port wired to the MODBUS network is configured to communicate with the ‘Metering’ Flow Computer on that network. Check settings for baud rate, character format, handshaking, signal standard and MODBUS specific parameters. (Note: Refer to Chapter 7 of this manual for a full guide to 7951 Serial Communications).

2. Navigate to: <“Configure”>/<“Other parameters”>/<“Communications”>/<“MODBUS master”>



Slave device 1 func Edit the option selected to be “FC PROVER”.

Slv device 1 port no Edit the option descriptor that corresponds to the serial port that is connected to the same MODBUS network as the ‘Metering’ Flow Computer.

Slv device 1 address ‘SET’ a value to be the same as the MODBUS address of the ‘Metering’ 7951.

4. Navigate to this menu: <“Proving”>/<“Device to prove”>

5. Change the option selected to be “Device 1”.

(Steps 6 to 9 are for the ‘Metering’ 7951 Flow Computer)

6. Ensure that the port wired to the network is configured to communicate with the ‘Proving’ Flow Computer on that network. Check settings for Baud rate, Character format, Handshaking, Signal standard and MODBUS specific parameters.

7. Navigate to this menu: <“Configure”>/<“Other parameters”>/<“Communications”>/<“Ports”>

8. Select the sub-menu for the port that is wired to the network.



Comms port owner Change the selection to “Modbus slave”.

P MODB slave add Set a value for the MODBUS base address of this ‘Metering’ Flow Computer.

P Modbus Features Change the selection to include “Alarm”. This allows the ‘Metering’ Flow Computer to inform the ‘Proving’ Flow Computer of new alarms.

‡‡ This 7951 must also have D-type connectors and be running the same release of the software.


Page 16A.40 7951 2510 (CH16A/CB)

16A.8 Operating a Prove Session This sub-section shows how a prove-session should be operated. The emphasis is placed on use of the 7951 front panel keyboard. However, it is possible to manipulate the various data locations from over a MODBUS network link.

Trouble-shooting sub-sections are included here to explain the cause of proving related alarms and session error messages.

Use this table to quickly locate the pages:

Section Purpose of Section 1st Page

16A.8.1 Step-by-step instructions on operating a Bi-directional Proving Session. 16A.41

16A.8.2 Step-by-step instructions on operating a Unidirectional Proving Session. 16A.45

16A.8.3 Step-by-step instructions on operating a Brooks Compact Proving Session. 16A.48

NoticeExpressions of the form <“Configure”>/<“Prover”> translate into the following front panel keyboard sequences:

(1) Press the MAIN-MENU Button.

(2) Use the DOWN-ARROW button to scroll through several pages. Halt when “Configure” appears.

(3) Press the lettered-button that is alongside that description.

(4) Use the DOWN-ARROW button to scroll through several pages. Halt when the description “Prover” appears.

(5) Press the lettered-button that is alongside that description.

Note: Valves must be in the correct initial position prior to starting a prove session – the block valve must be open and the divert valve must be closed. Failure to observe this, results in a “Prover Abort Init i” alarm.


7951 2510 (CH16A/CB) Page 16A.41

16A.8.1 Operating a Bi-directional Proving Session Follow these instructions: 1. Review existing session settings and adjust if necessary

Prover max runs Select the total number of prove-runs for a prove session.

Prover req good runs Select the number of consecutive good (passed) prove-runs required for a successful proving session.

Device to prove Select the slave device number as set-up in the earlier configuration task

2. Start a session

(2a) Navigate to this menu: <“Proving”>

(2b) Locate this Parameter: <”Prover control”>

(2c) Change the option selected to be “Start”. Note: A session can be aborted at any time by selecting the “Stop” option.

3. Monitor the progress of a prove-run

(3a) Navigate to this menu: <“Proving”>/<“Prover progress”>

(3b) Monitor the <“Prover progress”> parameter for one full prove-run

Messages (as displayed)

Instructions and Comments

Opening outlet valve Manual Control (Individual confirmation mode only):Open the Prover Outlet valve and then answer ‘yes’ to the on-screen prompt.

Manual Control (Group confirmation mode only): See “Valves aligned?” message prompt.

Automatic Control:No action required. The valve is commanded to be ‘fully’ open. The 7951 expects an ‘open’ valve state to be returned within a set time limit for this valve.

Opening inlet valve Manual Control (Individual confirmation mode only):Open the Prover Isolation (Inlet) valve and then answer ‘yes’ to the on-screen prompt.



Closing block valve Manual Control (Individual confirmation mode only):Close the Metering-run Block valve and then answer ‘yes’ to the on-screen prompt.

Manual Control (Group confirmation mode only): See “Valves aligned?” message prompt. Automatic Control:No action required. The valve is commanded to be fully closed. The 7951 expects an ‘close’ valve state to be returned within a set time limit for this valve.

Valves aligned? Yes No

Manual Control (Group confirmation mode only): Open the Prover Outlet valve, open the Prover Isolation (Inlet) valve, close the Metering-run Block valve and then answer “Yes” to the on-screen prompt. Answering “No” will abort the session.

Valves aligned No action required. Flow should be entering the Prover-loop.


Page 16A.42 7951 2510 (CH16A/CB)


Stabilisation. Stabilisation .. Stabilisation ...

Wait for the stabilisation period to end. The length of time for this was set during a configuration task.

Prover PreRun init No operator action required. This message is not usually seen.

Diverter valve fwd Manual Control:Position the 4-way Diverter valve to the ‘forward’ position and then answer ‘yes’ to the on-screen prompt. Automatic Control:

No action required. The 4-way Diverter valve is commanded to the ‘forward position. The 7951 expects a ‘forward’ valve state to be returned within a set time limit for thisvalve.

Note: Subsequent prove runs start with this message.

Ball release No operator action required. The ‘Proving’ 7951 automatically signals the Prover to launch the ‘displacer’. A set amount of time is allowed for the Prover to launch the ‘displacer’ and then the next message appears.

Ball launch No operator action required. The ‘displacer’ is now expected to be moving towards the ‘start’ detector.

Start sensor detect No operator action required. The ‘Proving’ 7951 is now waiting for the Prover to send it a pulse to indicate that the ‘displacer’ has reached the ‘start’ detector. It is then known to be moving towards the ‘end’ detector. A set amount of time is allowed for this wait. The session is aborted if this time limit is reached without receiving a pulse. (See “Prover Abort” alarm description)

End sensor detect No operator action required. Flowmeter pulses are now being counted by the ‘proving’ 7951. The ‘Proving’ 7951 is now waiting for the Prover to send a pulse to indicate that the ‘displacer’ has reached the ‘end’ detector. It is then known to be moving towards the launching mechanism. A set amount of time is allowed for this wait. The session is aborted if this time limit is reached without receiving a pulse.

Ball returning No operator action required. Flowmeter pulses have stopped being counted by the 7951. The ‘displacer’ is now moving to the launching mechanism. A set amount of time is allowed for this to be completed and then the next message appears.

Diverter valve rev Manual Control:Position the 4-way Diverter valve to the ‘reverse’ position and then answer ‘yes’ to the on-screen prompt.

Automatic Control:No operator action required. The 4-way Diverter valve is commanded to the ‘reverse’ position. The 7951 expects a ‘reverse’ valve state to be returned within set time limit for ‘valve #4’. The next message appears when valve state is received.

Ball release No operator action required. The ‘Proving’ 7951 automatically signals the Prover to launch the ‘displacer’. A set amount of time is allowed for the Prover to launch the ‘displacer’ and then the next message appears.

Ball launch No operator action is required. The ‘displacer’ is now expected to be on way towards the ‘start’ detector.

Start sensor detect No operator action is required. The ‘Proving’ 7951 is now waiting for the Prover to send it a pulse to indicate that the ‘displacer’ has reached the ‘start’ detector. It is then known to be moving towards the ‘end’ detector. A set amount of time is allowed for this wait. The session is aborted if this time limit is reached without receiving a pulse.


7951 2510 (CH16A/CB) Page 16A.43

End sensor detect No action required. Flowmeter pulses are now being counted by the 7951. The ‘Proving’ 7951 is now waiting for the Prover to send it a pulse to indicate that the ‘displacer’ has reached the ‘end’ detector. It is then known to be moving towards the launching mechanism. A set amount of time is allowed for this wait. The session is aborted if this time limit is reached without receiving a pulse.

Ball returning No action required. Flowmeter pulses have stopped being counted by the 7951. The ‘displacer’ is now returning to the interchange mechanism. A set amount of time is allowed for this to be completed and then the next message appears.

Proving completed No operator action required. The prove-run is complete. Calculations now take place to produce a ‘Meter Factor’. Subsequent prove-runs start by re-positioning the 4-way Diverter valve. (Refer back to the “Diverter valve fwd” message)

4. Quickly navigate to the menu <“Proving”>/<“Prover current run”> to see the run number is now showing a ‘1’ instead of a ‘0’.

5. Re-navigate to this menu: <“Proving”>/<“Prover progress”> and monitor the close of a session.



Proving session completedPress any key.

Press any button on the 7951 front panel keyboard. The next message will then appear.

New mf xxxxxx.xx Old mf xxxxxx.xx

AcceptDisregard

This message will not appear if the minimum number of consecutive good prove-runs is not achieved or if a new ‘K factor’ is required instead of a new ‘Meter Factor’.

Press the blue ‘c’ button to accept the new ‘Meter Factor’ and allow it to be used in the next Corrected Volume flow rate calculation. The value is then written to the <“Meter factor”> Parameter. Press the blue ‘d’ button to NOT accept the new ‘Meter Factor’ and re-use the old ‘Meter Factor’. Note: Modbus control of this prompt is done through the parameter <”Prv store result”>. It is located within this menu: <“Proving”>/<“Remote action”>.

New kf xxxxxx.xx Old kf xxxxxx.xx

AcceptDisregard

This message will not appear if the minimum number of consecutive good prove-runs is not achieved or if a new ‘Meter factor’ is required instead of a ‘K factor’.

Press the blue ‘c’ button to accept the new ‘K factor’ and allow it to be used in the next Indicated Volume flow rate calculation. The value is then written to the <“Turb K factor”> Parameter. Press the blue ‘d’ button to NOT accept the new ‘K factor’ and re-use the old ‘K Factor’. Note: Modbus control of this prompt is done through the Parameter: <”Prv store result”>. It is located within this menu: <“Proving”>/<“Remote action”>.

Prove print report Yes No

Press the blue ‘c’ button to transmit an ASCII report through the port that is configured for a direct connection to a printer.

Press the blue ‘d’ button to NOT print a report

Opening block valve Manual Control (Individual confirmation mode only): Open the Metering-run Block valve and then answer ‘yes’ to the on-screen prompt.




Page 16A.44 7951 2510 (CH16A/CB)


Closing inlet valve Manual Control (Individual confirmation mode only): Open the Prover Isolation (Inlet) valve and then answer ‘yes’ to the on-screen prompt.


Automatic Control:No action required. The valve is commanded to be ‘fully’ closed. The7951 expects a ‘closed’ valve state to be returned within a set time limit for this valve.

Closing outlet valve Manual Control (Individual confirmation mode only): Open the Prover Outlet valve and then answer ‘yes’ to the on-screen prompt.


Automatic Control:No action required. The valve is commanded to be ‘fully’ closed. The 7951 expects a ‘closed’ valve state to be returned within a set time limit for this valve.


Manual Control (Group confirmation mode only): Open the Metering-run Block valve, close the Prover Isolation (Inlet) valve, close the Prover Outlet valve and then answer “Yes” to the on-screen prompt. Answering “No” will abort the session.

Valves returned No action required. Flow should not be entering the Prover-loop.

End of prv session No action required. The normal Prover Report is transmitted through a serial port.

6. Navigate to the menu <“Proving”>/<“Last meter factor”> to see the new meter factor number.

7. Review information recorded from the session.

(End of Bi-directional Proving Session)


7951 2510 (CH16A/CB) Page 16A.45

16A.8.2 Operating a Unidirectional Proving Session Follow these instructions:

1. Review existing session settings and adjust if necessary


Device to prove Menu: <”Proving”>

Local ‘flowmeter’ proving:

Select “Device 1”.

Remote ‘flowmeter’ proving:

Select an option that corresponds to a MODBUS networked 7951 (slave device) that is providing metering-run information to the ‘proving’ 7951.



2. Start a session (2a) Navigate to this menu: <“Proving”> (2b) Locate this parameter: <”Prover control”> (2c) Change the option selected to be “Start”. Note: A session can be aborted by selecting the “Stop” option.

3. Monitor the progress of a prove-run (3a) Navigate to the menu: <“Proving”>/<“Prover progress”> (3b) Monitor the <“Prover progress”> parameter for one full prove-run



Opening outlet valve Manual Control (Individual confirmation mode only): Open the Prover Outlet valve and then answer ‘yes’ to the on-screen prompt.



Opening inlet valve Manual Control (Individual confirmation mode only): Open the Prover Isolation (Inlet) valve and then answer ‘yes’ to the on-screen prompt.



Closing block valve Manual Control (Individual confirmation mode only): Close the Metering-run Block valve and then answer ‘yes’ to the on-screen prompt.


Automatic Control:No action required. The valve is commanded to be fully closed. The 7951 expects a ‘close’ valve state to be returned within a set time limit for this valve.


Page 16A.46 7951 2510 (CH16A/CB)




Valves aligned No action required. Flow should be entering the Prover-loop.

Stabilisation. Stabilisation .. Stabilisation ...

Wait for the stabilisation period to end. The length of time for this was set during a configuration task.


Start prove run No operator action required. The ‘Proving’ 7951 automatically signals the Prover to launch the ‘displacer’. A set amount of time is allowed for the Prover to launch the ‘displacer’ and then the next message appears.

Ball launch No operator action required. The ‘displacer’ is now expected to be moving towards the ‘start’ detector.

Start sensor detect No operator action required. The ‘Proving’ 7951 is now waiting for the Prover to send it a pulse to indicate that the ‘displacer’ has reached the ‘start’ detector. It is then known to be moving towards the ‘end’ detector. A set amount of time is allowed for this wait. The session is aborted if this time limit is reached without receiving a pulse.

End sensor detect No operator action required. Flowmeter pulses are now being counted by the ‘proving’ 7951. The ‘Proving’ 7951 is now waiting for the Prover to send a pulse to indicate that the ‘displacer’ has reached the ‘end’ detector. It is then known to be moving towards the launching mechanism. A set amount of time is allowed for this wait. The session is aborted if this time limit is reached without receiving a pulse.

Ball returning No operator action required. Flowmeter pulses have stopped being counted by the 7951. The ‘displacer’ is now moving to the launching mechanism. A set amount of time is allowed for this to be completed and then the next message appears.

Proving finished No operator action required. The prove-run is complete. Calculations now take place to produce a new ‘Meter Factor’. Subsequent prove-runs are started by launching the ‘displacer’.

4. Select the menu <“Proving”>/<“Prover current run”> to see the run number is showing a ‘1’ instead of a ‘0’.







AcceptDisregard


Press the blue ‘c’ button to accept the new ‘Meter Factor’ and allow it to be used in the next Corrected Volume flow rate calculation. The value is then written to the <“Meter factor”> Parameter. Press the blue ‘d’ button to NOT accept the new ‘Meter Factor’ and re-use the old ‘Meter Factor’.

Note: Modbus control of this prompt is done through the parameter <”Prv store result”> It is located within this menu: <“Proving”>/<“Remote action”>.


7951 2510 (CH16A/CB) Page 16A.47



AcceptDisregard

This message will not appear if the minimum number of consecutive good prove- runs is not achieved or if a new ‘Meter factor’ is required instead of a new ‘K factor’.

Press the blue ‘c’ button to accept the new ‘K factor’ and allow it to be used in the next Indicated Volume flow rate calculation. The value is then written to the <“Turb K factor”> Parameter. Press the blue ‘d’ button to NOT accept the new ‘K factor’ and re-use the old ‘K Factor’. Note: Modbus control of this prompt is done through the parameter <”Prv store result”>









Automatic Control:No action required. The valve is commanded to be ‘fully’ closed. The7951 expects a ‘closed’ valve state to be returned within a set time limit for this valve.







End of prv session No action required. The normal Prover Report is transmitted through a serial port.

6. Navigate to the menu <“Proving”>/<“Last meter factor”> to see the new meter factor number.

7. Review information recorded from the session.

(End of Unidirectional Proving Session)


Page 16A.48 7951 2510 (CH16A/CB)

16A.8.3 Operating a Brooks Compact Proving Session Follow these instructions:

1. Review existing session settings, and adjust if necessary:

Parameters (as displayed)


Proving device Menu: <”Proving”>

Local ‘flowmeter’ proving:

Select “Device 1”.

Remote ‘flowmeter’ proving:

Select an option that corresponds to a Modbus networked 7951 (slave device) that is providing metering-run information to the ‘proving’ 7951.

Metering-run Select a metering-run.



2. Start a session (2a) Navigate to this menu: <“Proving”> (2b) Locate this parameter: <”Prover control”> (2c) Change the option selected to be “Start”. Note: A session can be aborted by selecting the “Stop” option.

3. Monitor the progress of a prove-run (3a) Navigate to the menu: <“Proving”>/<“Prover progress”>. (3b) Monitor the <“Prover progress”> parameter for one full prove-run.

Messages Instructions and Comments

Start hydraulic pump No operator action required. The ‘Proving’ 7951 automatically signals the Prover to start retracting the ‘displacer’ to the standby position. A set amount of time is allowed for the Prover to do this before the next message appears.

Upstream status No operator action. A set amount of time, <”Prv inter-run delay”>, is allowed for the Prover to signal that the ‘displacer’ (piston) is in the standby position. The session is aborted when this time limit is reached and the Prover has not signalled the 7951.

Opening outlet valve Manual Control (Individual confirmation mode only): Open the Prover Outlet valve and then answer ‘yes’ to the prompt.


Automatic Control:No action required. Valve is commanded to be fully open. 7951 expects an ‘open’ valve state to be returned within a set time limit for this valve.

Opening inlet valve Manual Control (Individual confirmation mode only): Open the Prover Isolation (Inlet) valve and then answer ‘yes’ to the on-screen prompt.




7951 2510 (CH16A/CB) Page 16A.49


Closing block valve Manual Control (Individual confirmation mode only): Close the Metering-run Block valve and then answer ‘yes’ to the on-screen prompt.


Automatic Control:No action required. The valve is commanded to be fully closed. The 7951 expects an ‘close’ valve state to be returned within a set time limit for this valve.



Valves aligned No operator action required. Flow should now be entering the Prover-loop.

Stabilisation. Stabilisation.. Stabilisation...

No operator action required. Plenum pressure is at the required level. Now wait for the stabilisation period to end. The length of time for this was set during a configuration task.

Plenum pressure. Plenum pressure.. Plenum pressure... Plenum pressure....

No operator action required. Wait for Plenum pressure to reach the required level. The length of time for this was set during a configuration task. Failure to get the Prover to achieve the required level results in the session being aborted.


Start prove run No operator action required. The ‘Proving’ 7951 automatically signals the Prover to launch the ‘displacer’. A set amount of time is allowed for the Prover to launch the ‘displacer’ and then the next message appears.

Piston launch No operator action required. The ‘displacer’ (piston) is now expected to be moving towards the ‘start’ detector.

Start sensor detect

No operator action required. The ‘Proving’ 7951 is now waiting for the Prover to send it a pulse to indicate that the ‘displacer’ has reached the ‘start’ detector. It is then known to be moving towards the ‘end’ detector. A set amount of time is allowed for this wait. The session is aborted if this time limit is reached without receiving a pulse.

End sensor detect

No operator action required. Flowmeter pulses are now being counted by the ‘proving’ 7951. The ‘Proving’ 7951 is now waiting for the Prover to send a pulse to indicate that the ‘displacer’ has reached the ‘end’ detector. A set amount of time is allowed for this wait. The session is aborted if this time limit is reached without receiving a pulse.

Piston returning

No operator action required. Flowmeter pulses have stopped being counted by the 7951. The ‘displacer’ (piston) is now returning to the up-stream position. A set amount of time is allowed for this to be completed and then the next message appears.

Stop hydraulic pump No operator action required. The ‘Proving’ 7951 automatically signals the Prover to stop moving the ‘displacer’. A set amount of time is allowed for the Prover to do this before the next message appears.

Proving finished No operator action required. The prove-run is complete. Calculations now take place to produce a new ‘Meter Factor’. Subsequent prove-runs are started by the 7951 re-launching the ‘displacer’.


Page 16A.50 7951 2510 (CH16A/CB)

4. Select the menu <“Proving”>/<“Prover current run”> to see the run number is showing a ‘1’ instead of a ‘0’.



Proving session Completed Press any key.



AcceptDisregard


Press the blue ‘c’ button to accept the new ‘Meter Factor’ and allow it to be used in the next Corrected Volume flow rate calculation. The value is then written to the <“Meter factor”> Parameter of the ‘Metering 7951’ or the ‘Metering/Proving 7951’. Press the blue ‘d’ button to NOT accept the new ‘Meter Factor’ and re-use the existing ‘Meter Factor’. Note: Modbus control of this prompt is done through the parameter <”Prv store result”>. It is located within this menu: <“Proving”>/<“Remote action”>.


AcceptDisregard

This message will not appear if the minimum number of consecutive good prove-runs is not achieved or if a new ‘Meter factor’ is required instead of a new ‘K factor’.

Press the blue ‘c’ button to accept the new ‘K factor’ and allow it to be used in the next Indicated Volume flow rate calculation. The value is then written to the <“Turb K factor”> Parameter of the ‘Metering 7951’ or the ‘Metering/Proving 7951’.

Press the blue ‘d’ button to NOT accept the new ‘K factor’ and re-use the existing ‘K Factor’.Note: Modbus control of this prompt is done through the parameter <”Prv store result”>














7951 2510 (CH16A/CB) Page 16A.51





End of prv session No action required. The Brooks Prover Report is transmitted through a serial port.

6. Navigate to the menu <“Proving”>/<“Last meter factor”> to see the new meter factor number

7. Review information recorded from the session

(End of Brooks Compact Proving Session)


Page 16A.52 7951 2510 (CH16A/CB)

16A.9 Archiving of Proving Information The 7951 instrument is permanently configured to record proving information in a tamper-proof archive. Information (data values) from an entire session, including all prove-passes and prove-runs, is stored in the Prover Archive. The capacity of this archive is 1 session.

A complete set of values from any prove-pass§§ and any prove-run of the session can be displayed for viewing or for retrieval by an external Modbus networked device, but can not be printed out through a serial port. Editing of an archived value is not possible. Each attempt to edit a displayed value (from the archive) will see an “*** Access denied ***” message.

Although the Prove Archive is a fixed size and operates independently of all other data archiving activities, it is worth reading about other Archiving facilities (see Chapter 9). The Prover Archive display is located within this menu: <“Proving”>/<“Prover log”>.

16A.9.1 Archived Session Parameter

Parameters * What is this data?

Prv session status Final status of the proving session.

Prv new meter factor Generated ‘Meter factor’.

Prove start time Date and time that the session commenced.

Prv duration Total amount of time for the entire session.

Prv MF deviation ‘Meter factor’ deviation value for the session. The lowest deviation is 0.00.

Prv old meter factor The existing/previous ‘Meter factor’ from the ‘Metering 7951’.

Prover new K factor Generated ‘K factor’.

Prover old K factor The existing/previous ‘K factor’ from the ‘Metering 7951’.

Prv interp pulses The interpolated pulse count from all good prove-runs.

Prv ave meter temp The average fluid temperature (at the flow point) from all the good prove-runs.

Prv ave meter press The average pressure (at the flow metering point) from all the good prove-runs.

Prv ave flow rate Averaged rate of flow in the prover-loop – from all good prove-runs.

Prv meter freq Prover pulse frequency – from all good prove-runs.

Prv ave base dens Average fluid density value (at base conditions) from all good prove-runs.

Prv CTS The temperature correction factor for the steel pipe-work of the Prover.

Prv CPS The pressure correction factor for the steel pipe-work of the Prover.

Prv CTLP Correction factor for the effect of temperature on the fluid in the Prover-loop.

Prv CPLP Correction factor for the effect of pressure on the fluid in the Prover-loop.

Prv CTLM Correction factor for temperature effect on fluid flowing through the meter under test

Prv CPLM Correction factor for pressure effect on the fluid flowing through the meter under test

Prv corr prover vol The Prover base volume that has been corrected for temperature and pressure effects on the liquid and the steel

Prv metered volume This volume given by dividing <”Prv interp pulses”> with <”Prover old K factor”>

Prv corr metered vol The metered volume corrected for temperature and pressure effects on the fluid flowing through the meter under test.

Prv MF deviation The difference between the new ‘Meter factor’ and the old ‘Meter factor’.

* Abbreviations: “Prv” = Prover, “interp” = interpolated, “temp” = temperature, “freq” = frequency, “ave” = average “press” = pressure, “dens” = density, “corr” = corrected, “MF” = Meter factor, “vol” = volume

§§ Applicable only when using a Brooks Compact Prover. A full prove-run consists of one or more passes (volume sweeps).


7951 2510 (CH16A/CB) Page 16A.53

16A.9.2 Archived Prove-run Parameter (Use the <”View prove run data”> parameter to choose another prove-run: 0 = last run, 1 = 1st run, etc.)


Prv run status This shows the final status of the prove-run

Prv run prv temp Average of Prover Inlet and Outlet temperature measurements taken during the run

Prv run prv press Average of Prover Inlet and Outlet pressure measurements taken during the run

Prv run stream temp Average of all the temperature measurements during the prove-run

Prv run stream press Average of all the pressure measurements during the prove-run

Prv run strm volrate Average of all Indicated Volume flow rate values during the prove-run

Prv run freq The count of interpolated pulses received from the flowmeter during the prove-run.

Prv run meter fact A ‘Meter factor’ value. Calculated using values generated from the prove-run.

Prv run pulse count Uncorrected pulse count for the prove-run

Prv run corr pulse Corrected (interpolated) pulse count for the prove-run

Prv run TDVOL This is the time between the piston reaching the ‘start’ detector and the piston reaching the ‘end’ detector. (See page 16A.10 for details)

Prv run TDFMP This is the timing for correcting a pulse count from a volume sweep. Turn to page 16A.10 for details

Prv run base temp The ‘SET’ base temperature at the beginning of the prove-run.

* Abbreviations: “Prv” = Prover, “interp” = interpolated, “temp” = temperature, “freq” = frequency, “press” = pressure,

“dens” = density, “corr” = corrected, “MF” = Meter factor, “volrate” = volume flow rate,

“strm” = stream, “fact” = factor

16A.9.3 Archived Brooks Compact Prove-pass Parameter (Use <”View prove pass data”> to choose another volume sweep: 0=last pass, 1=1st, 2=2nd, etc.)


Prv pass pulse count The uncorrected pulse count for a single pass of the presently selected prove-run

Prv pass corr pulse The interpolated pulse count for a single pass of the presently selected prove-run

Prv pass TDVOL This is the time between the piston reaching the ‘start’ detector and the piston reaching the ‘end’ detector. (See 16A.10 for details)

Prv pass TDFMP This is the timing for correcting a pulse count from a volume sweep. Turn to page 16A.10 for details.

Prv pass flow rate The Indicated Volume flow rate value at the start of a prove-pass.

* Abbreviations: “Prv” = Prover, “corr” = corrected


Page 16A.54 7951 2510 (CH16A/CB)

16A.10 Prover Reporting The ‘Proving’ 7951 offers to print-out a proving report at the end of a prover session. Alternatively, it can be printed at any time by a making an appropriate selection from within the PRINTER (button) menu. This section shows a sample of each proving report.

16A.10.1 Print Requests using the front panel keyboard

(Ensure that one serial port is configured for the connection to a printer)


1. Press the grey PRINT-MENU button

2. Navigate to this menu: <“Print report”>/<“Print”>

3. Press the ‘b’ button

4. Use the UP-ARROW button to scroll through the list of reports

5. Press the ENTER button when “Prover report” appears on line two.


7951 2510 (CH16A/CB) Page 16A.55

16A.10.2 Bi-directional Prove Summary Reports (Prove by volume and mass)

Prove Summary Report - Volume -----------------------------Prove report number: 34 Site location:Start time: 13/12/2001 14:47:40 Duration: 107.000 s

Prover Details --------------Prover type Bi-direction AC Base volume 10.000 m3 @ cal temp 20.000 Deg.C Internal dia 200.000 mm, wall thickness 10.000 mm Prover tube material 304 st steel, Modulus of E 193053196000.000 N/m2 Prv expansion coeff 0.000 PPM/Deg.C,

Meter Details -------------Meter run 2 Meter serial number: 2 Meter number 2Manufacturer Flow Calibration factor(s) _________________________________

Fluid Type: _________________________________

Pulse scaling factor: _________________________________

Density source: _________________________________

Old K factor 0.180 pulse/m3, old meter factor 0.997 Count deviation 0.000 %, MF deviation 0.000 %

Run Data --------Run Interp -Temperature- --Pressure--- Flow Rate Base Dens Meter Meter Sts pulses Prover Meter Prover Meter freq factor --- Deg.C--- ---bar abs--- m3/s kg/m3 Hz 1 3270.976 15.000 15.000 10.021 10.000 1.181 789.645 168.000 0.001 OK2 3270.978 15.000 15.000 10.021 10.000 1.181 789.645 168.000 0.001 OK--------------------------------------------------------------------------------Avg:3270.977 15.000 15.000 10.021 10.000 1.181 789.645 168.000

Prover Data -----------(1) Base volume of prover 10.000 m3 (2) CTSp: Correction for temperature on steel 1.00000 (3) CPSp: Correction for pressure on steel 1.00009 (4) CTLp: Correction for temperature on liquid 1.00000 (5) CPLp: Correction for pressure on liquid 1.00080 (6) CCFp: Combined correction factor (2*3*4*5) 1.00089 (7) Corrected prover volume (1 * 6) 10.009 m3

Meter Data ----------(8) Metered volume (avg. pulse / previous K factor) 18172.095 m3 (9) CTLm: Correction for temperature on liquid 1.00000 (10) CPLm: Correction for pressure on liquid 1.00080 (11) CCFm: Combined correction factor (9 * 10) 1.00080 (12) Corrected meter volume (8 * 11) 18186.598 m3

Meter Factor (MF) -----------------(13) New meter factor (7 / 12) 0.00055 (14) New K factor (previous K factor / 13) 327.06660 (15) MF deviation from previous (((max-min)/avg)*100) 99.945 %

Remarks: ________________________________________________________________________

________________________________________________________________________ Signature: Date: Company: ____________________ ______________ _____________________ Signature: Date: Company: ____________________ ______________ _____________________


Page 16A.56 7951 2510 (CH16A/CB)

Prove Summary Report - Mass ---------------------------Prove report number: 13 Site location:Prove start time: 11/12/2001 11:50:39 Duration: 300.000 s

Prover Details --------------Prover Company:Prover unit serial No.Prover type Bi-direction AC Base volume 10.000 m3 @ cal temp 20.000 Deg.C Internal dia 200.000 mm, wall thickness 10.000 mm Prover tube material 304 st steel, Modulus of E 193053196000.000 N/m2 Prv expansion coeff 0.000 PPM/Deg.C,

Meter Details -------------Meter run 4 Meter serial number: Undefined Meter number UndefinedManufacturer:Model:

Manufactor Flow calibration factor(s)________________________________

Pulse scaling factor: ________________________________

Fluid Type: ________________________________

Density source: ________________________________

Old K factor 0.250 pulse/kg, old meter factor 1.000 Count deviation 0.000 %, MF deviation 0.000 %

Run Data --------Run Interp Prover Prover Flow Rate Base Dens Meter Meter Sts pulses Temp Press freq factor Deg.C bar abs kg/hour kg/m3 Hz 1 1947.015 15.000 10.000 1439991.6 789.645 99.999 1.015 OK2 1947.011 15.000 10.000 1440014.6 789.645 100.001 1.015 OK3 1947.013 15.000 10.000 1439994.9 789.645 100.000 1.015 OK4 1947.012 15.000 10.000 1439998.3 789.645 100.000 1.015 OK5 1947.014 15.000 10.000 1440010.6 789.645 100.001 1.015 OK--------------------------------------------------------------------------------Avg:1947.013 15.000 10.000 1440002.0 789.645 100.000

Prover Data -----------(1) Base volume of prover 10.000 m3 (2) Base density of prover 789.645 kg/m3 (3) CTSp: Correction for temperature on steel 1.00000 (4) CPSp: Correction for pressure on steel 1.00009 (5) CTLp: Correction for temperature on liquid 1.00000 (6) CPLp: Correction for pressure on liquid 1.00080 (7) CCFp: Combined correction factor (3*4*5*6) 1.00089 (8) Corrected prover mass (1*2*7) 7903.484 kg

Meter Data ----------(9) Metered mass (avg. pulse / previous K factor) 7788.052 kg

Meter Factor ------------(10) New meter factor (8 / 9) 1.01482 (11) New K factor (previous K factor / 10) 0.24635 (12) MF deviation from previous (((max-min)/avg)*100) 1.482 %

Remarks: ________________________________________________________________________



7951 2510 (CH16A/CB) Page 16A.57

16A.11 Trouble-shooting Guide This section provides reference information for finding out why a prove-run and/or prove-session was not successful. The principal 7951 areas to examine are the alarm log messages and the status error messages.

16A.11.1 Prove Session Alarms Session related alarms can be seen in the History Alarm Log.

Base Alarm Message What caused this alarm to appear?

Prover Abort (Prove session aborted) A reason is indicated by the additional letter after the “Prover Abort” message: ‘V’ = Valve alignment failed or Prover is not ready ; ‘i’ = Valves not in correct initial position or communications not set-up correctly for

local/remote proving or no flow in run being proved (check flow status location). ‘I’ = Pre-prove run (Complete configuration tasks) ‘L’ = Leakage detected ‘c’ = All prove runs completed ‘S’ = Incomplete metering-run configuration ‘s’ = Conditions not stable ‘p’ = Plenum pressure target not achieved.

Prover limit A reason is indicated by the additional letter after the “Prover limit” message: ‘F’ = Flow rate difference between Meter-run and Prover ‘T’ = Temperature difference between Meter-run and Prover ‘P’ = Pressure difference between Meter-run and Prover ‘M’ = Meter factor difference between Meter-run and Prover ‘E’ = Error pulses detected ‘R’ = Brooks Compact Prover is not signalling that it is ready for proving. ‘a’ = Prover Archive too small – software fault occurred

Prover timeout A reason is indicated by the additional letter after the “Prover timeout” message: ‘S’ = ‘Displacer’ did not reach the ‘start’ detector within a set time limit ‘E’ = ‘Displacer’ did not reach the ‘end’ detector within a set time limit

Valve failed A ‘fail’ valve state was received by the 7951. The additional character identifies the valve: ‘1’ = Valve one (Prover Isolation valve), ‘2’ = Valve two (Prover Outlet valve) ‘3’ = Valve three (Metering-run Block valve), ‘4’ = Valve four (4-way diverter valve)

Valve timeout Valve has not responded within a set time limit. The additional character identifies the valve: ‘1’ = Valve one (Prover Isolation valve), ‘2’ = Valve two (Prover Outlet valve) ‘3’ = Valve three (Metering-run Block valve), ‘4’ = Valve four (4-way diverter valve)

16A.11.2 Session Error Messages Status messages can be seen in the <“Proving”>/<“Prover progress”> menu.

Message What caused this message to appear?

Inlet valve failed Outlet valve failed Block valve failed Diverter valve fail

(1) Valve state indicates that it has suffered a failure, or (2) Valve did not respond within a set time limit.

Start sensor timeout Start pulse not received from first detector switch within set time limit. End sensor timeout End pulse not received from final detector switch within set time limit. Prover error pulses Turbine error pulses detected during pulse count.

Prove aborted See Alarm “Prover Abort”.


Page 16A.58 7951 2510 (CH16A/CB)

16A.12 Miscellaneous Reference Information 16A.12.1 Proving sequence flowcharts and timing diagrams

Abort state

Abort state

No Yes

(Increase"Prover run number")

No

Yes

Abort state or"Prover run timeout" = 0

Abort state or"Prover start timeout" = 0

Stabilsationcompleted

Prover control = "Start"

Valves aligned

Abort state or"Prv stable timeout" = 0

Manual valve control(Valve duration = 0) Automatic valve control

(Valve duration > 0)

Prover controlis "idle"

INITIALISE

ALIGN VALVES

STABILISE

Abort state orValve failed state

RETURN VALVES

START

RUN

STOP

Calculate a newmeter factor

Max provesor

Finished session

Automaticvalve

control

Start pulse detected

End pulse detected

Figure 16.7: Unidirectional Proving Sequence


7951 2510 (CH16A/CB) Page 16A.59

End pulse detected


End pulse detected


Abort state

No Yes

(Increase"Prover run number")

No

Yes


Abort state or"Prover start timeout" = 0

Stabilsationcompleted

Prover control = "Start"

Valves aligned

Abort state or"Prv stable timeout" = 0

Manual valve control(Valve duration = 0) Automatic valve control

(Valve duration > 0)

Prover controlis "idle"

INITIALISE

ALIGN VALVES

STABILISE

Abort state orValve failed state

RETURN VALVES

ROTATE 4-WAYDIVERTER (forward)

PROVE RUN

Calculate a newmeter factor

Max provesor

Finished session

Automaticvalve

control

STOP

ROTATE 4-WAYDIVERTER (reverse)

PROVE RUN (return)

STOP


Figure 16.8: Bi-directional Proving Sequence


Page 16A.60 7951 2510 (CH16A/CB)

16A.12.2 Uni/Bi-directional Prover Timing Diagram

The following timing diagram describes a normal Unidirectional (or Bi-directional proving) session operation.

Stabilise

Start Delay

Start Timeout

Run Timeout

End Delay

Inter-Run Delay

Repeat for each Prover Run

Start

Proving

Status Outputs

Timing Parameters

(Start Sensor Timeout)

(End Sensor Timeout)

‘Start timeout’ & ‘run timeout’ indicate a sensor detect or timeout.


7951 2510 (CH16A/CB) Page 16A.61

16A.12.3 Brooks Compact Prover Timing Diagram The following timing diagram describes a normal Brooks Compact proving session operation.

Status Outputs

Timing parameters

Start Hydraulic Pump

Stop Hydraulic Pump

Upstream status

Run command

Plenum press charge

Plenum press vent

Status Inputs

Valves alignment

Stabilise

Plenum pressure

Inter-Run delay/Upstream status tmo

Start delay

Start timeout

Run timeout

End delay

Inter-Run delay/upstream tmo

Start detect

End detect

Prover ready

Pre condition Prover run Prover run End of prv session

Start hydraulic pump

Stop hydraulic pump


Page 16A.62 7951 2510 (CH16A/CB)

Chapter 16(b) Master Meter Proving

7951 2510 (CH16b/AB) Page 16b.1

16B. Master Meter Proving

16B.1 What is the purpose if this chapter? This chapter has been written to provide a guide to the 7951 flow computer software and hardware support for Master Meter Proving.

To use this guide effectively, it is essential to be familiar with the general proving support (in Chapter 16A) and be familiar with the 7951 button functions and the menu system. (Chapter 5 can help with this)

The data necessary for configuring a measurement/feature can be found in separate parts of the menu structure. A notation has therefore been used as a short method of explaining how to move from the present menu to another menu.





Step 4: Use the DOWN-ARROW button to scroll through pages until the “Flow rate” is seen.

Step 5: Press the lettered-button that is alongside the “Flow rate” descriptor.

Sometimes, it is more convenient to use the MAIN-MENU button (especially if lost). However, use of the BACK-ARROW button is a much more common method of returning to a previous menu level.


16B.2 Master meter proving (with a 7951 single-run flow computer) What to do here: Read the overview that starts on this page. Understand the input and outputs that are listed in Section 16B.4. Review the configuration details in Section 16B.5. Review the operating instructions in Section 16B.6.

Overview Master Meter Proving is intended to allow in-situ proving of a turbine/PD or Coriolis flow meter against an infrequently used, high integrity (so-called master) meter.

Various combinations of methods are supported: Volumetric master meter proving a turbine meter for volume. Volumetric master meter proving a mass coriolis meter for mass. Coriolis mass master meter proving a mass coriolis meter for mass. Coriolis mass master meter proving a turbine meter for volume.

The main principle is that the meter-under-test and the ‘master’ meter are directly compared in terms of flow over a criteria-controlled period. Criteria for ending a comparison can be either attaining a pre-set number of pulses or a pre-set volume of flow. Differences from the comparison form the basis for generating a new flow correction factor. MF (Meter factor) calculations are shown in on page 16b.3. In common with pipe proving support, valve alignments, stabilisation checking, and flow factor validations all feature in master meter proving. (Also, see page 16B.6 for a tour of a typical proving session)


Page 16b.2 7951 2510 (CH16b/AB)

Local and Remote Proving Support Local and remote proving of meters is supported. With two pulse inputs available on a 7951, it can be connected to: 1 x local metering-run (stream) or 1 x ‘remote’ metering-run (stream) via another 7951. Pulse input 2 is reserved for the master meter.

A ‘local’ meter-run connection involves direct – point-to-point – wiring to field instrumentation (sensors, valve controllers and flowmeter) of a single meter-run (run).

A ‘remote’ meter-run connection involves MODBUS networked 7951 flow computers. The ‘remote’ 7951 flow computer requires direct – ‘local’ meter-run – connections to field instrumentation.

Additionally, pulses from the ‘local’ meter-run meter must also be directed, by some external switching circuitry, into Pulse Input 2 of the ‘proving’ 7951.

Proving Control Proving related functions are largely controlled by a 7951 flow computer. Proving sessions are operated from the front panel of the 7951 or by MODBUS communications between the 7951 and a host.

Valve Support Valve control and monitoring support is optional and is as described in the valves section of Chapter 16(A). Master meter proving involves metering-run block valves (see “HSO/C 1821” in Figure 16B.2.1Error! Reference source not found.) and prover inlet valves 1 (see “HSO/C 1831”). A general configuration is shown in Figure 16B.2.1Error! Reference source not found.. All the 7951 flow computer connections are as guided in Section 16B.4 of this addendum.

Note: In the software menus, the prover inlet valve is known as “Valve 1”, the block valve is “Valve 3” and the prover outlet valve is “Valve 2”.

Figure 16B.2.1: General Metering Configuration

Turbine 1

Turbine 2

Master Turbine

Inlet

Inlet

HSO/C 1821

HSO/C 1831

Outlet

HSO/C 1851

HSO/C 1841

HSO/C 1861

1 Where there is also a prover outlet valve, it is necessary to control the prover outlet valve and the prover inlet valve with the same

pair of status outputs. Monitor state outputs from either the prover inlet valve or the prover outlet valve.


7951 2510 (CH16b/AB) Page 16b.3

16B.3 Master Meter Proving Calculations The Master Meter Proving calculations for each scenario are listed here for your convenience. To avoid duplication of information, it is also necessary to refer to the calculation section in Chapter 16A.

Unless otherwise stated, calculation terms here are annotated with parameters as displayed within the Prover Archive (Master Meter) prove-run menus.

16B.3.1 Volumetric Master Meter Proving of a Volumetric Meter (for volume)

MMP#1: Corrected Meter-under-test Volume

Using: mutCV = CplmCtlmmutKf

NC

V** * Parameter value copied from ‘Metering’ 7951

Where:

CVmut = Corrected Meter-under-test Volume….…………...{Parameter: <”Prv run CorMeterVol”>}

NC = Interpolated count of pulses (Meter-under-test)……..….....……{See Calculation MMP#3}

Ctlm = Correction factor for effect of temperature on fluid at the Meter-under-test……….……… …………………………………………………..…………….{Parameter: <”Prv run CTLm”>}

Cplm = Correction factor for effect of pressure on fluid at the Meter-under-test…………..………. …………………………………………………..…………….{Parameter: <”Prv run CPLm”>}

KfVmut = Current ‘K factor’ for Meter-under-test (in volumetric units)………..……………..………..... …………………………………………………….………..{Parameter: <”Prv run MUT K F”>} *

Calculation Note: Refer to Chapter 16(A) calculations for further information on the CTL and CPL factors

MMP#2: Corrected ‘Master Meter’ Prover Volume

Using: mmCV = CpspCtspCplpCtlpMFmmKf

PCmm

V*****

Where:

CVmm = Corrected ‘Master Meter’ Prover Volume…….…………{Parameter: <”Prv run corr vol”>}

PC = Pulse count (Master Meter)……………………….…{Parameter: <”Prv run pulse count”>}

MFmm = Existing ‘Meter Factor’ for Master Meter……..……{Parameter: <”Prv run MM MFactor”>}

Ctlp = Correction factor for effect of temperature on fluid at the Master Meter…………………… …………………………………………………..…..………….{Parameter: <”Prv run CTLp”>}

Cplp = Correction factor for effect of pressure on fluid at the Master Meter……………………….. …………………………………………………..…..………….{Parameter: <”Prv run CPLp”>}

Ctsp = Correction factor for effect of temperature on the Master Meter…………………….……… ………………………………...………………..…..………….{Parameter: <”Prv run CTSp”>}

Cpsp = Correction factor for effect of pressure on the Master Meter………………………………… ……………………………..……………………….………….{Parameter: <”Prv run CPSp”>}

KfVmm = Current ‘K factor’ for Master Meter (in volume units)………..…………………………………

………………………………………………………... {Parameter: <”Prv run MM K Factor”>}

Calculation Note: Refer to Chapter 16(A) calculations for further information on the CTL and CTS factors


Page 16b.4 7951 2510 (CH16b/AB)

MMP#3: Interpolated Pulse Count

Using: NC =mut

mutmm t

Pulsest *

Where:

NC = Interpolated count of pulses (Master Meter)………. {Parameter: <”Prv run corr pulse”>}

tmm = Time to collect Master Meter pulses………..…….... {No Parameter}

tmut = Time to collect pulses from the Meter-under-test…. {No Parameter}

MMP#4: New ‘Meter-under-test’ Meter Factor

Using: MFNEW = mutmm

CVCV ……………………………………..…….…… {Parameter: <”Prv run meter factor”>}


7951 2510 (CH16b/AB) Page 16b.5

16B.3.2 Volumetric Master Meter Proving of a Coriolis Mass Meter (for Mass)

MMP#5: Indicated ‘Meter-under-test’ Mass

Using: mutIM = mutKf

NCM

* Parameter value copied from ‘Metering’ 7951

Where: IMmut = Indicated Mass (Meter-under-test)………………{Parameter: <”Prv run SUT ind mass”>}


KfMmut = Current ‘K factor’ for Meter-under-test (in pulse/mass or mass/pulse units) ……………… …………………………………………………….………..{Parameter: <”Prv run MUT K F”>} *

MMP#6: Corrected ‘Master Meter’ Prover Mass

Using: mmCM = PmmM

CpspCtspMFmmKf

PC ****

Where: PC = Pulse count (Master Meter) ……………………...…{Parameter: <”Prv run pulse count”>}

MFmm = Existing ‘Meter Factor’ of the Master Meter………{Parameter: <”Prv run MM MFactor”>}

Ctsp = Correction factor for effect of temperature on the Master Meter……………………………. ………………………………...……………….…..………….{Parameter: <”Prv run CTSp”>}

Cpsp = Correction factor for effect of pressure on the Master Meter…………………...…………… ………………………………...………..……..…..………….{Parameter: <”Prv run CPSp”>}

KfMmm = Current ‘K factor’ of Master Meter (in pulse/mass or mass/pulse units) ……….…..……… ……………………………………………..………... {Parameter: <”Prv run MM K Factor”>}

P = Master Meter fluid density……………...…………………………{See Calculation MMP#7}


MMP#7: Master Meter fluid density

Using: P = BCplpCtlp **

Where: Ctlp = Correction factor for effect of temperature on fluid at the Master Meter………………..….

………………………………...……………….…..………….{Parameter: <”Prv run CTLp”>}

Cplp = Correction factor for effect of pressure on fluid at the Master Meter………………………. ………………………………...……………….…..………….{Parameter: <”Prv run CTLp”>}

P = Base density……………………………………..…….{Parameter: <”Base density value”>}


MM#8: New ‘Meter-under-test’ Meter Factor

Note: The product mass does not change with the effects of temperature and pressure. Hence, Indicated Mass (IM) is used when deriving the Meter Factor (MF) for the meter-under-test.


IMCM …………………………….………………..{Parameter: <”Prv run meter factor”>}


Page 16b.6 7951 2510 (CH16b/AB)

16B.3.3 Coriolis Mass Master Meter Proving a Coriolis Mass Meter (by Mass)

MMP#9: Indicated ‘Meter-under-test’ Mass

Using: mutIM = mutKf

NCM

* Parameter value copied from ‘Metering’ 7951

Where: IMmut = Indicated Mass (Meter-under-test)………………{Parameter: <”Prv run SUT ind mass”>}


KfMmut = Current ‘K factor’ for Meter-under-test (in pulse/mass or mass/pulse units) ……………… …………………………………………………….………..{Parameter: <”Prv run MUT K F”>} *

MMP#10: Corrected ‘Master Meter’ Prover Mass

Using: mmCM = CpspCtspMFmmKf

PCmm

M***

Where:

PC = Pulse count (Master Meter) ……………………...…{Parameter: <”Prv run pulse count”>}


Ctsp = Correction factor for effect of temperature on the Master Meter……………………………. ………………………………...……………….…..………….{Parameter: <”Prv run CTSp”>}

Cpsp = Correction factor for effect of pressure on the Master Meter…………………...…………… …………………………….…..………..……..…..………….{Parameter: <”Prv run CPSp”>}

KfMmm = Existing ‘K factor’ of Master Meter (in pulse/mass or mass/pulse units) …………..……… ……………………………………………..…...….... {Parameter: <”Prv run MM K Factor”>}

MMP#11: New ‘Meter-under-test’ Meter Factor

Note: The product mass does not change with the effects of temperature and pressure. Hence, Indicated Mass (IM) is used when deriving the Meter Factor (MF) for the meter-under-test.


IMCM …………………………………………..…..{Parameter: <”Prv run meter factor”>}


7951 2510 (CH16b/AB) Page 16b.7

16B.3.4 Coriolis Mass Master Meter Proving a Volumetric Meter (by Volume)

MMP#12: Corrected Meter-under-test Volume

Using: mutCV = CplmCtlmmutKf

NC

V** * Parameter value copied from ‘Metering’ 7951

Where: CVmut = Corrected Meter-under-test Volume….…………...{Parameter: <”Prv run CorMeterVol”>}


Ctlm = Correction factor for effect of temperature on fluid at the Meter-under-test……….……… …………………………………………………..…………….{Parameter: <”Prv run CTLm”>}

Cplm = Correction factor for effect of pressure on fluid at the Meter-under-test…………..………. …………………………………………………..…………….{Parameter: <”Prv run CPLm”>}

KfVmut = Current ‘K factor’ for Meter-under-test (in volumetric units)……………………..………..... …………………………………………………….………..{Parameter: <”Prv run MUT K F”>} *

Calculation Note: Refer to Chapter 16(A) calculations for further information on the CTL and CPL factors

MM#13: Corrected ‘Master Meter’ Prover Volume

Using: mmCV =P

mmM

CpspCtspMFmmKf

PC ***

Where: PC = Pulse count (Master Meter) ……………………...…{Parameter: <”Prv run pulse count”>}


Ctsp = Correction factor for effect of temperature on the Master Meter…………………….……… ………………………………...………………..…..………….{Parameter: <”Prv run CTSp”>}

Cpsp = Correction factor for effect of pressure on the Master Meter………………………………… ……………………………..……………………….………….{Parameter: <”Prv run CPSp”>}

P = Master Meter fluid density…………………………………………{See Calculation MMP#7}


MMP#14: Master Meter fluid density

Using: P = BCplpCtlp **

Where: Ctlp = Correction factor for effect of temperature on fluid at the Master Meter………………..….

………………………………...……………….…..………….{Parameter: <”Prv run CTLp”>}

Cplp = Correction factor for effect of pressure on fluid at the Master Meter………………………. ………………………………...……………….…..………….{Parameter: <”Prv run CTLp”>}

P = Base density……………………………………..…….{Parameter: <”Base density value”>}


MM#15: New ‘Meter-under-test’ Meter Factor


CVCV …………………………………………..……{Parameter: <”Prv run meter factor”>}


Page 16b.8 7951 2510 (CH16b/AB)

16B.4 Input and output connections for master metering This section is a guide to the inputs and outputs that are required by master meter proving when using a 7951 flow computer.

A summary is given in Table 16B.4.1 for you to understand the split required when there is a remote ‘Metering’ flow computer. The tables that follow this summary give further details of the connections.

Table 16B.4.1: Summary of master metering connections

7951 ‘Prover’ flow computer 7951 ‘Metering’ flow computer

Digital (Status) Inputs for Prover outputs Digital (Status) Inputs for valve monitoring

Digital (Status) Outputs for Prover inputs Digital (Status) Outputs for open/close valve control

Pulse input 1 for local/remote meter Pulse Input 2 for master flowmeter Pulse Input 1 for the local meter

Port for MODBUS communications with remote flow computer – i.e. the slave device

Port for communications with ‘Prover’ 7951 flow computer – i.e. the Master MODBUS device

Prover Inlet and Outlet sensors Metering-run (stream) sensors

Note: When there is only ‘local’ proving required, the combined ‘proving’ and ‘Metering’ 7951 requires all connections

Digital Inputs: (Digital Input wiring information can be found in Chapter 2)

Status Input No. *

D-type Rear Panel Pin Comment

4 SK4/4 Strainer blockage Input. Active = Blockage + Abort Prove. Read Note A

10 SK4/14

11 SK4/15 10=Prover inlet valve state ‘A’ : 11=Prover inlet valve state ‘B’ Called “Valve 1” in software. (Also, read Notes B and C)

12 SK4/16

13 SK4/17 12=Block valve state ‘A’ : 13=Block valve state ‘B’ Called “Valve 3” in software. (Also, read Notes B and C)

Applicable notes are listed at the end of this Chapter section

Pulse Inputs: (Pulse Input wiring information can be found in Chapter 2)

Pulse Input Comment

1 Meter pulse count from ‘local’ or ‘remote’ meter-run flowmeter (Coriolis – support only for single pulse train with no IP252 checking)

2 Master Meter pulse count only - no IP252 checking

Note: Configuration parameters for pulse input connections are as guided in Chapter 11

Analog Inputs: (Analogue Input wiring information can be found in Chapter 2)

Measurement * Comment

Master Meter Inlet Temperature Wire element from master meter to a PRT Input on 7951 (4 wire)

Master Meter Outlet Temperature Wire element from master meter to a PRT Input on 7951 (4 wire)

Master Meter Inlet Pressure Wire element from master meter to a 4-20mA input (2 wire)

Master Meter Outlet Pressure Wire element from master meter to a 4-20mA input (2 wire)

* Where an installation does not have separate field transmitters for the prover inlet and outlet measurements, you may nominate the same analog channel for both measurements.


7951 2510 (CH16b/AB) Page 16b.9

Digital Outputs: (Digital Output wiring information can be found in Chapter 2)

StatusOutput *

D-type Rear Panel Pin Comment

7 SK5/6 ‘Active’ = Start Prove 12 SK5/16 13 SK5/17

12=Prover inlet valve control ‘A’ : 13=Prover inlet valve control ‘B’ Called “Valve 1” in software. (Also, read Notes B and C)

14 SK5/18 15 SK5/19

14=Block valve control (A) : 15=Block valve control (B) Called “Valve 3” in software. (Also, read Notes B and C)

Note: When about to start proving a meter, ensure the valve positions of other metering-runs (streams) will not interfere with the proving. Incorrect positioning of valves can prevent the session from starting. Master meter proving will only manipulate the valves related to the meter-under-test.

MODBUS Communications Network Link: This is required when a 7951 flow computer is dedicated to proving functions, whilst remote 7951 flow computer is dedicated to normal ‘metering’ functions. The flow computers must be interconnected to form a MODBUS network and allow the ‘proving’ 7951 to obtain metering specific data from a remote flow computer for use in a prove session. Refer to Chapter 7 for guidance on MODBUS network connections.

Input/Output Connection Notes:A There is a software switch (Parameter) for determining if a blocked strainer is detected by a digital (status)

input or by mA input. By default, the digital (status) input method is selected for all strainers. Status Input 4 is allocated to the strainer input; it can be changed using the <Strainer Din source> parameter but you must take care to not clash with the Master Meter digital input/output map.

Unless the mA method is required, no further configuration is required and the digital inputs table, shown earlier, has a map of these related inputs.

To change over to the 4-20mA (DP) Input method:

Navigate to this menu: <"Configure">/<"Inputs">/<"Strainer input"> Work through the menu-based parameters as guided in Parameter List 16B.4.1.

To revert to using a digital (status) input:

Navigate to this menu: <"Configure">/<"Inputs">/<"Strainer input"> Locate the menu-based parameter with “Strainer input src” and edit the option to show “Digital input”.

B Valve status signals are received through paired Status Inputs (nominated as ‘A’ and ‘B’ in the DigitalInputs table). Each valve is allocated a separate pair of inputs. The combinations of active and inactive inputs are then used to differentiate the valve states – see Table 16B.4.2

C Valve control commands are issued through paired Status Outputs (nominated as ‘A’ and ‘B’ in the DigitalOutputs table). Each valve is allocated a separate pair. Combinations of active and inactive outputs from the paired outputs are used to differentiate the valve commands – see Table 16B.4.3.

Parameter List 16B.4.1: Parameters for 4-20mA (DPIT) Strainer Input

Parameters Comments and Instructions

Strainer input src Select the option descriptor containing “mA input”.Strainer Ain source Select the analogue input channel used by the device.

Strainer DP @ 100% Edit a full-scale DP value.Strainer DP @ 0% Edit a value for the lowest DP measurement.Strainer DP HI limit ‘Set’ the threshold for detection of a blockage. *

Note: Analogue Input wiring examples can be found in Chapter 2. * Should the selected mA input channel fail, it will also be interpreted as a blockage.


Page 16b.10 7951 2510 (CH16b/AB)

Table 16B.4.2: Logic Table for Determining Valve States

‘A’ ‘B’ Valve State Comment 0 0 Failed This indicates the existence of a fault condition. 0 1 Open Valve is fully open 1 0 Close Valve is fully closed 1 1 Moving Valve is being re-positioned

Key: ‘1’ = Active, ‘0’ = Inactive

Table 16B.4.3: Valve Commands

‘A’ ‘B’ Command Comment 0 0 Idle Valve remains at present position 0 1 Open Fully open valve 1 0 Close Fully close valve 1 1 (Not Used) Never issued from the flow computer


7951 2510 (CH16b/AB) Page 16b.11

16B.5 Configuration Tasks: Proving Details This section explains how to configure basic details for master meter proving and how a proving session should operate. There are separate communication set-up tasks for ‘local’ proving and ‘remote’ proving.

Mini-Index

16B.5.1 Configuration Task #1: Meter-run Measurement Functions…………………. 16b.12

16B.5.2 Configuration Task #2: Common Prover details……………….………………16b.14

16B.5.3 Configuration Task #3: Master Meter Proving Details………………..……… 16b.17

16B.5.4 Configuration task #4a: Serial Port Communications (‘local’ prove………… 16b.18

16B.5.5 Configuration task #4b: Serial Port Communications (‘remote’ prove)….…..16b.19


Page 16b.12 7951 2510 (CH16b/AB)

16B.5.1 Configuration Task #1: Meter-run Measurement Functions

(Unless indicated, this task is to be attempted on the flow computer performing the ‘Metering’ functions)


1. Ensure that the following measurements/features are configured.

Measurement task Parameter pages to check Which 7951 FC?

Flow meter details (Various - See Chapter 11) ‘Proving’ and ‘Metering’

Flow rates (Various - See Chapter 11) ‘Metering’

Metering density Meter density ‘Metering’

Base density Base density value ‘Metering’

Metering temperature Meter temperature ‘Metering’

Metering pressure Meter pressure ‘Metering’

Note: Refer to Chapter 11 for information on configuration these measurements/features

2. Prover inlet and outlet temperature measurements. Objective: Get ‘LIVE’ measurement values on the ‘proving’ 7951.

What to do:(2a) Navigate to this menu: <“Configure”>/<“Temperature”>/<“Prover temp”> (2b) Work through this parameter list:


Inlet temp @ 100% SET a value for the maximum temperature that is supported by the transmitter. THIS IS NOT APPLICBLE IF USING HART.

Inlet temp @ 0% SET a value for the minimum temperature that is supported by the transmitter. THIS IS NOT APPLICBLE IF USING HART.

Inlet temp source Edit the selection to be the description that corresponds to the input used by the sensor.

Inlet temp LO lmt SET a lower limit for the scaled inlet temperature value. An alarm will be raised when this lower limit is exceeded.

Inlet temp HI lmt SET a higher limit for the scaled inlet temperature value. An alarm will be raised when this higher limit is exceeded.

Inlet temp FB type (Optional) Select a fallback function - “Last good value” or “Fallback value” - for when the transmitter can not provide a live value.

Inlet temp FB val (Optional) SET a value for the “Fallback value” function (if it is selected).

Inlet temp offset (Optional) Use this for on-line calibration of the transmitter

Prover inlet temp Change the status to be “LIVE”.

Outlet temp @ 100% SET a value for the maximum temperature that is supported by the transmitter. THIS IS NOT APPLICBLE IF USING HART.

Outlet temp @ 0% SET a value for the minimum temperature that is supported by the transmitter. THIS IS NOT APPLICBLE IF USING HART.

Outlet temp source Edit the selection to be the description that corresponds to the input used by the sensor.

Outlet temp LO lmt SET a low limit for the scaled inlet temperature value. An alarm will be raised when this lower limit is exceeded.

Outlet temp HI lmt SET a high limit for the scaled inlet temperature value. An alarm will be raised when this higher limit is exceeded.


7951 2510 (CH16b/AB) Page 16b.13

Outlet temp FB type (Optional) Select a fallback function - “Last good value” or “Fallback value” - for when the transmitter can not provide a live value.

Outlet temp FB val (Optional) SET a value for the “Fallback value” function (if it is selected).

Outlet temp offset (Optional) Use this for on-line calibration of the transmitter.

Prover outlet temp Change the status to be “Live”.

3. Prover inlet and outlet pressure measurements.

Objective: Get scaled pressure measurement values.

What to do:(3a) Navigate to this menu: <“Configure”>/<“Temperature”>/<“Prover pressure”>

(3b) Work through this parameter list:


Inlet press @ 100% ‘Set’ a value for the maximum pressure that is supported by the transmitter. THIS IS NOT APPLICBLE IF USING HART.

Inlet press @ 0% ‘Set’ a value for the minimum pressure that is supported by the transmitter. THIS IS NOT APPLICBLE IF USING HART.

Inlet press source Edit the selection to be the description that corresponds to the input used by the sensor.

Inlet press LO lmt ‘Set’ a lower limit for the scaled Inlet Pressure value. An alarm will be raised when this lower limit is exceeded.

Inlet press HI lmt ‘Set’ a higher limit for the scaled Inlet Pressure value. An alarm will be raised when this higher limit is exceeded.

Inlet press FB type (Optional) Select a fallback function - “Last good value” or “Fallback value” - for when the transmitter can not provide a live value.

Inlet press FB val (Optional) ‘Set’ a value for the “Fallback value” function (if it is selected).

Prover inlet press Change the status to be “Live”.

Outlet press @ 100% ‘Set’ a value for the maximum pressure that is supported by the transmitter. THIS IS NOT APPLICBLE IF USING HART.

Outlet press @ 0% ‘Set’ a value for the minimum pressure that is supported by the transmitter. THIS IS NOT APPLICBLE IF USING HART.

Outlet press src Edit the selection to be the description that corresponds to the input used by the sensor.

Outlet press LO lmt ‘Set’ a low limit for the scaled Inlet Pressure value. An alarm will be raised when this lower limit is exceeded.

Outlet press H lmtI ‘Set’ a high limit for the scaled Inlet Pressure value. An alarm will be raised when this higher limit is exceeded.

Outlet press FB type (Optional) Select a fallback function - “Last good value” or “Fallback value” - for when the transmitter can not provide a live value.

Outlet press FB val (Optional) ‘Set’ a value for the “Fallback value” function (if it is selected).

Prover outlet press Change the status to be “Live”.


Page 16b.14 7951 2510 (CH16b/AB)

16B.5.2 Configuration Task #2: Common Prover details

(Unless indicated, this task is to be attempted on the flow computer performing the ‘Proving’ functions)

Objectives: Identify the type of Proving required. Provide fundamental information about that Proving Set limits for the MF (Meter factor) validation process and the stabilisation phase Set time-outs for the various proving events Provide optional information for a printed report.

What to do:Follow these instructions: 1. Navigate to one of these menus:

(a) <“Configure”>/<“Inputs”>/<”Flow meter”>/<”Turbine/PD details”>/<”Prover turbine/PD”> or(b) <“Configure”>/<“Inputs”>/<”Flow meter”>/<”Coriolis meter”>/<”Prover coriolis”>

2. Work through this Parameter list. (Some menu searching is required) Parameters Instructions and Comments

Prover meter freq Change status to “LIVE”. (NB. ‘Master’ meter is connected to Pulse Input 2)

Prove freq hi limit Optional alarm limit threshold for the max. ‘Master’ meter pulse frequency

Prv flow stop thresh Minimum tolerated pulse frequency from ‘Master’ meter before Flow Stop

Prover meter factor SET the MF value as given on the calibration sheet for the ‘Master’ meter

3. Navigate to this menu: <“Configure”>/<“Prover”>/<”Common prv details”>

4. Work through this Parameter list. (Some menu searching is required)


Prover type Select “Master Meter Turb” only if the Master Meter (Prover) is outputting a frequency representing volume. Otherwise, nominate “Master Meter Cori”.

Prove by Vol Mass Select either to prove by volume or by mass(See Section 16B.3 for the various proving scenarios that are supported.)

Prover IO assign Select a ‘Master Meter’ option. This action nominates a valve control and monitoring scheme. (Also, see Section 16B.4 for a map of inputs/outputs)

Prv pipe inner dia SET a value for the inner diameter of pipe (at the ‘master’ meter position)

Prv wall thickness SET a value for the thickness of the of pipe (at the ‘master’ meter position)

Modulus of E SET a value for the modulus of elasticity

Prover cal temp ‘Set’ a value for the temperature at which the ‘master’ meter was calibrated.

Site name (Optional) Edit a site name to be included in the Prover Report.

Meter serial number (Optional) Edit a text label to be included in the Prover Report.

Meter number (Optional) Edit a text label to be included in the Prover Report.

“Vol” = Volume, IO = Input Output, “Prv” = Prover/Prover, “dia” = diameter, “cal” = calibration

5. Navigate to this menu: <“Configure”>/<“Prover”>/<”Common prv operatn”>

6. Work through this parameter list: (Some menu searching is required)


Prv operation Select the form of interaction between the operator and the ‘Proving’ 7951

Prover calc select Select option to calculate a new ‘Meter Factor’



7951 2510 (CH16b/AB) Page 16b.15


Prover req good runs Select the number of consecutive good (passed) prove-runs required for ending a session.

Prv meter factor dev SET a limit (%) for the tolerated deviation for MF values from all prove-runs out of the completed sequence of consecutive passed runs. (NB. 100% switches off this limit)

The deviation calculation and subsequent limit check forms the first part of the MF (Meter factor) validation process. (Also, see pulse count deviation and MF limit check)

Exceeding the index limit will not raise an alarm but it does trigger a fresh attempt to get a complete sequence of consecutive good (passed) prove-runs out of the remaining session.

(The MF deviation calculation is shown under note B)

Prv interp pulse dev SET a limit (%) for the tolerated deviation of pulse counts from all prove-runs out of the completed sequence of consecutive passed runs. (NB. 100% switches off this limit)

This deviation calculation and subsequent limit check forms a middle part of the MF (Meter factor) validation process. It is not performed if the first part of the MF check failed.

Exceeding the index limit will not raise an alarm but it does trigger a fresh attempt to get a complete sequence of consecutive good (passed) prove-runs out of the remaining session.

(The interpolated pulse count deviation calculation is shown under note C)

Prv meter factor LO

Prv meter factor HI

SET a low limit for the average of MF values from all prove-runs out of the completedsequence of consecutive passed runs.

This limit check is the final part of the MF (Meter Factor) validation process and is performed only if the MF deviation is within limits.

Exceeding the limit will not raise an alarm but it does trigger a fresh attempt to get a complete sequence of consecutive good (passed) prove-runs out of the remaining session.

(Read note A)

Prover start delay SET a value for a delay just before the prove-run starts. A zero value = no delay.

Prover start timeout SET a zero value for this delay. It is not applicable to this type of proving

Prover run timeout SET a value for the maximum time allowed for a prove-run to complete (including any programmed delays). A zero value is equivalent to no time allowed

Prv inter-run delay SET a value for the period between any start/end delay for prove-runs during a session. A zero value is equivalent to no time delay

Prover end delay SET a value for a delay immediately following the completion of a prove-run. A zero value is equivalent to no time delay

Prv temperature diff SET a limit for the maximum allowed difference between the operating fluid temperature for the meter-under-test flow point and the averaged temperatures at the Prover Inlet/Outlet valves. This parameter limit check occurs at the end of a prove-run. (Also, read note E)

Prv pressure diff SET a limit for the maximum allowed difference between the operating pressure for the meter-under-test flow point and the averaged pressures at the Prover Inlet/Outlet valves.This parameter limit check occurs at the end of a prove-run. (Also, read note E)

Prv flow rate diff SET a value for the maximum difference between flow at the ‘meter-under-test’ and the ‘master’ meter – checked once every machine cycle and at end of a run. (Also, read note E)

Prv stable timeout SET a value for the period to allow temperatures, pressures and rates of flow to stabilise following valve alignments. This stabilisation phase occurs as soon as valves are aligned. (Also, see limit parameters that follow)


Page 16b.16 7951 2510 (CH16b/AB)


Prv stable temp diff SET a value for the maximum allowed difference between the fluid temperature at the ‘meter-under-test’ flow point and the averaged fluid temperatures at the Prover Inlet/Outlet valves. (Also, read note D)

Prv stable pres diff SET a value for the maximum allowed difference between pressure at the meter-under-test flow point and the averaged pressures at the Prover Inlet/Outlet valves. (Read note D)

Abbreviations used: “Prv” = Prove or Prover, “calc” = calculation, “max” = maximum, “req” = required, “dev” = deviation, “interp” = interoplated, “diff” = difference

See next page for associated notes

Notes: A MF (Meter factor) validation occurs when there is a number of consecutive good (passed) prove-runs is equal

to the parameter value of <”Prover req good runs”>.

When the validation check is successful, the session is brought to a graceful end. Otherwise, a fresh attempt is made to get consecutive good runs.

(See notes B and C for calculations performed during the MF validation check)

B A deviation calculation is performed at the time of a MF (Meter factor) validity check. (Also, see note A)

Using: MFR = 100*Ave

LowHigh

MFMFMF

Where: MFR = Deviation (%)………………….…….…….….. {Parameter: <”Prv meter factor dev”>}

HighMF = Highest ‘meter factor’ from completed sequence of passed prove-runs

LowMF = Lowest ‘meter factor’ from completed sequence of passed prove-runs

And: AveMF =2

LowHigh MFMF

C A pulse count deviation calculation is performed as a part of the MF (Meter factor) validation check.

Using: NCR = 100*Ave

LowHigh

NCNCNC

Where: NCR = Pulse count deviation (%)…………….…..... {Parameter: <”Prv interp pulse dev”>}

HighNC = Highest pulse count from completed sequence of passed prove-runs LowNC = Lowest pulse count from completed sequence of passed prove-runs

And: AveNC =2

LowHigh NCNC

D This limit is applied once every machine cycle for the duration of the stabilisation phase. Exceeding the limit will not raise an alarm but it will trigger a fresh attempt to detect stability for 10 consecutive machine cycles during the remainder of the phase.

E Exceeding this limit will raise an alarm and record the prove-run as a failure. A fresh attempt is then made to get the required number of consecutive good (passed) prove-runs from the remainder of the session.


7951 2510 (CH16b/AB) Page 16b.17

16B.5.3 Configuration Task #3: Master Meter Proving Details

(Unless indicated, this task is to be attempted on the flow computer performing the ‘Proving’ functions)


1. Navigate to this menu: <“Configure”>/<“Prover”>/<”Master Meter”>

2. Work through this Parameter list.


MM run criteria A prove-run is delimited by achieving an indicated volume or pulse count.

MM Pulses required SET a value if the Master Meter (and/or Meter-run Meter) pulse count is the criteria for completion of a run.

Prover Volume SET a value if indicated volume of flow measured during a prove-run is the criteria for completion of the run.

Prv expansion coeff SET a value for the prover expansion coefficient.

Prv sqr expan coeff SET a value for the area expansion coefficient.

MM material Free-form text required for the Prover Report.

MM serial number Free-form text required for the Prover Report.

MM meter number Free-form text required for the Prover Report.

Abbreviations: “Prv” = Prover, “MM” = Master Meter, “expan” = expansion, “coeff” = coefficient, “sqr” = square


Page 16b.18 7951 2510 (CH16b/AB)

16B.5.4 Configuration task #4a: Serial Port Communications (‘local’ prove)

Objective: Set-up for a combined ‘Metering’ and ‘Proving’ flow computer.


1. Navigate to this menu: <“Configure”>/<“Other parameters”>/<“Communications”>/<“MODBUS master”>/<”Slave…”>

2. Work through Table 16B.5.1

Table 16B.5.1: Local Prove Parameters


Slave device 1 func Edit the option descriptor to be “FC PROVER”.

Slv device 1 address SET the value to 0 (for ‘local’ proving)

3. Navigate to the menu: <“Proving”>/<“Device to prove”>

4. Find the Parameter page with this description: <“Proving device”>

5. Edit the option to be “Device 1”

(End of Configuration Task)


7951 2510 (CH16b/AB) Page 16b.19

16B.5.5 Configuration task #4b: Serial Port Communications (‘remote’ prove)

Objectives:The ‘Proving’ 7951 flow computer should be set-up as a ‘Master’ on a MODBUS network. Other devices, such as the remote ‘Metering’ flow computer must be set-up as a ‘slave’ on a MODBUS network. This organisation allows:

1. Parameter values to be transmitted to the ‘Proving’ FC for use during a proving session 2. New meter factors to be forwarded to ‘Metering’ flow computer 3. The ‘Proving’ FC to ask the ‘Metering’ FC to control valves and 4. The ‘Metering’ FC to forward valve states to the ‘Proving’ FC.

To avoid repetition, the following instructions are written with the assumption that there is a single remote ‘Metering’ flow computer. It must be set-up as MODBUS slave.


(Steps 1 to 5 are for the ‘Proving’ flow computer)

1. Ensure that a communication port is wired to the same MODBUS network as the remote ‘Metering’ flow computer. Also, check the communication parameters on each flow computer.

(Note: Refer to Chapter 7 of this manual for a full guide to 7951 flow computer communications)

2. Navigate to: <“Configure”>/<“Other parameters”>/<“Communications”>/<“MODBUS master”>

3. Work through this Parameter list…


Slave device 1 func Edit the option selected to be “FC PROVER”.

Slv device 1 port no Edit the option descriptor that corresponds to the serial port that is connected to the same MODBUS network as the ‘Metering’ flow computer.

Slv device 1 address SET the value to be the same as the MODBUS address of the ‘Metering’ FC

Abbreviations: “func” = function, “Slv” = Slave, “no” = number

4. Navigate to this menu: <“Proving”>/<“Device to prove”>

5. Change the option selected to be “Device 1”.

(Steps 6 to 9 are for the ‘Metering’ flow computer)

6. Ensure that a communication port is wired to the same MODBUS network as the ‘proving’ 7951 flow computer. Also, check the communication parameters on each flow computer.

(Note: Refer to Chapter 7 of this manual for a full guide to 7951 flow computer communications)

7. Navigate to this menu: <“Configure”>/<“Other parameters”>/<“Communications”>/<“Ports”>

8. Select the sub-menu for the serial port that is wired to the MODBUS network.

9. Work through this Parameter list: (To avoid repetition, parameters are only listed for port one)

Parameter Instructions and Comments

Comms port1 owner Change the selection to “Modbus slave”.

P1 MODB slave add SET a value for the MODBUS base address of this ‘Metering’ flow computer.

P1 Modbus Features Change the selection to include “Alarm”. This allows the remote ‘Metering’ flow computer to inform the ‘Proving’ 7951 flow computer of new alarms.


Page 16b.20 7951 2510 (CH16b/AB)

16B.6 Operating a Prove Session This sub-section shows how a proving session should be operated. Emphasis is placed on use of the front panel keypad. However, the various parameters can be manipulated through a MODBUS network link.

Follow these instructions: 1. Review existing session settings and adjust if necessary


Prover req good runs Select the number of consecutive good (passed) prove-runs required for a proving session to be considered successful.

Proving device If ‘Local’ proving, select “Device 1”. Otherwise, select the MODBUS device number for the ‘remote’ flow computer associated with the ‘remote’ meter *

* Refer to Section 16B.5.5 on page 16b.19 if you need to remind yourself of the MODBUS Slave devices known to the ‘Proving’ 7951.

2. Start a session (2a) Navigate to this menu: <“Proving”> (2b) Locate this Parameter: <”Prover control”> (2c) Change the option selected to be “Start”.

Note: A session can be aborted at any time by selecting the “Stop” option.

3. Monitor the progress of a prove-run (3a) Navigate to this menu: <“Proving”>/<“Prover progress”> (3b) Monitor the <“Prover progress”> Parameter page. You will see a message sequence as below


Opening inlet valve Manual Control (+Individual confirmation mode only)Open the Prover Inlet valve and then answer ‘yes’ to the on-screen prompt.

Manual Control (Group confirmation mode only):See “Valves aligned?” message prompt.

Automatic Control:No action required. The valve is commanded to ‘fully’ open. The 7951 will then expect an ‘opened’ valve state to be returned within the ‘Set’ valve time limit.

Closing block valve Manual Control (+Individual confirmation mode)Close the Meter-run Block valve and then answer ‘yes’ to the on-screen prompt.

Manual Control (+Group confirmation mode)See “Valves aligned?” message prompt that follows.

Automatic Control:No action required. The valve is commanded to ‘fully’ close. The 7951 will then expect a ‘closed’ valve state to be returned within the ‘Set’ valve time limit.


Manual Control (Group confirmation mode only): Open the Prover Inlet valve, close the Meter-run Block valve and then answer “Yes” to the on-screen prompt. Answering “No” will abort the session.

Valves aligned No action required. Flow should be passing meter-under-test + master meter.

Stabilisation. Stabilisation.. Stabilisation...

The Stabilisation phase is as described in Chapter 16. Wait for the stabilisation period to end. The length of time for this is set during a configuration task.

Prover PreRun init No operator action required. This message is not seen unless the machine cycle time is over 2 seconds.


7951 2510 (CH16b/AB) Page 16b.21

Performing prove run Prove run in progress.


Press any button on the front panel keypad. The next message will then appear.

New MF xxxxxx.xx Old MF xxxxxx.xx

AcceptDisregard


Press the blue ‘c’ button to accept the new factor value and allow it to be used in the next machine cycle. Press the blue ‘d’ button to NOT accept the new factor value and, therefore, continue using the existing ‘Meter Factor’.


New KF xxxxxx.xx Old KF xxxxxx.xx

AcceptDisregard

This message will not appear if the minimum number of consecutive good prove-runs is not achieved or if a new ‘Meter factor’ is required instead of a new ‘K factor’.

Press the blue ‘c’ button to accept the new factor value and allow it to be used in the next machine cycle. Press the blue ‘d’ button to NOT accept the new factor value and, therefore, continue to use the existing factor value.


Prove print report? Yes No

Press the blue ‘c’ button to transmit a report through the port that is configured for a direct connection to an ASCII compatible output device (e.g. printer or terminal).

Press the blue ‘d’ button to NOT print a report at this time. It can always be printed later through the PRINTER MENU.

Opening block valve Manual Control (Individual confirmation mode)Open the meter-run block valve and then answer ‘yes’ to the on-screen prompt.

Manual Control (Group confirmation mode):See “Valves aligned?” message prompt.

Automatic Control:No action required. The valve is commanded to be ‘fully’ open. The 7951 will expect an ‘open’ valve state to be detected within a set time limit.

Closing inlet valve Manual Control (Individual confirmation mode)Open the Prover Inlet valve and then answer ‘yes’ to the on-screen prompt.

Manual Control (Group confirmation mode)See “Valves aligned?” message prompt.

Automatic Control:No action required. The valve is commanded to ‘fully’ close. The flow computer will then expect a ‘closed’ valve state to be detected within a set time limit.


Manual Control (Group confirmation mode)Open the Meter-run Block valve, close the Prover Isolation (Inlet) valve and then answer “Yes” to the on-screen prompt. Answering “No” will abort the session.

Valves returned No action required

End of prv session No action required. Optional report is transmitted through a communications port.

Note: Additional prompts appear when a batch transaction is in progress; these are for retrospective calculations. In addition, batch reports can be transmitted through a communication port during a prove session.

6. Navigate to the menu <“Proving”>/<“Last meter factor”> to see the accepted/unaccepted meter factor value.

7. Review information recorded from sessions by looking under the <”Prover”>/<”Prover log”>/<”Master Meter”> menu or (if printed) examining the “Master Meter Prover Report”.


Page 16b.22 7951 2510 (CH16b/AB)

16B.7 Archiving of Proving Information The 7951 is permanently configured to record proving information in a tamper-proof archive. Information (data values) from an entire session, including all prove-passes and prove-runs, is stored in the Prover Archive. The capacity of this archive is 1 session.

A complete set of values from any prove-run of the session can be displayed for viewing or for retrieval by an external Modbus networked device, but can not be printed out through a serial port. Editing of an archived value is not possible. Each attempt to edit a displayed value (from the archive) will see an “*** Access denied ***” message.

Although the Prove Archive is a fixed size and operates independently of all other data archiving activities, it is worth reading about other Archiving facilities (see Chapter 9.)

The Prover Archive display is located within this menu: <“Proving”>/<“Prover log”>/<”Master meter”>.

Table 16B.7.1: Archived Session Data


Prv session status Final status of the proving session.

Prv MM flow rate Average rate of flow at the master meter.

Prv old K factor Previous/existing K Factor.

Prover new K factor Generated K factor.

Prv old meter factor Previous/existing Meter Factor.

Prv new meter factor Generated Meter Factor.

Prv MF deviation Deviation figure for the Meter Factor generated after each prove-run.

Prv count deviation Uncorrected pulse count deviation.

MF dev (old/new) Deviation figure for the existing MF and the generated MF.

* Abbreviations: “Prv” = Prover, “MF” = Meter factor, “dev” = deviation

Table 16B.7.2: Archived Master Meter (MM) Prove-run Data

(Use the <”View prove run data”> parameter to choose another prove-run: 0 = last run, 1 = 1st run, etc.)

Parameters * What is this data? Prv run status Final status of selected prove-run.

Prv run pulse count Uncorrected pulse count for the prove-run.

Prv run MM K Factor K Factor generated at the end of the prove-run.

Prv run MM Ind Vol Indicated Volume rate of flow at the end of the prove-run.

Prv run MM Ind mass Indicated Mass rate of flow at the end of the prove-run.

Prv run prv temp Average of Prover Inlet and Outlet temperature measurements during the run.

Prv run prv press Average of Prover Inlet and Outlet pressure measurements during the prove-run.

Prv run MM MFactor Meter Factor generated at the end of the prove-run.

Prv run CTLp Correction Factor for effect of temperature on fluid passing the master meter.

Prv run CPLp Correction Factor for effect of pressure on fluid passing the master meter.

Prv run CTSp Correction Factor for effect of temperature on the prover-loop.

Prv run CPSp Correction Factor for effect of pressure on the prover-loop.

Prv run CCFp Combined Correction Factor – for prover-loop flow rates.

Prv run corr vol Corrected Prover Volume – See page 16b.3 for calculations.

PrvRun MM CorrPrvMas Correct Prover Mass – See page 16b.3 for calculations.

* Abbreviations: “Prv” = Prover, “ind” = indicated, “temp” = temperature, “press” = pressure, “MFactor” = Meter factor, “Vol” = volume, “corr” = corrected, “MM” = Master Meter, “Mas” = Mass


7951 2510 (CH16b/AB) Page 16b.23

Table 16B.7.3: Archived ‘Meter under test’ (MUT) Prove-run Data

(Use the <”View prove run data”> parameter to choose another prove-run: 0 = last run, 1 = 1st run, etc.)


Prv run corr pulse Corrected (interpolated) pulse count for the run – See page 16b.3 for calculations.

Prv run MUT K Factor K Factor generated at the end of the prove-run – See page 16b.3 for calculations.

Prv run MUT Ind Vol Meter-under-test Indicated Volume rate of flow at the end of the prove-run.

Prv run SUT ind mass Meter-under-test Indicated Mass rate of flow at the end of the prove-run.

Prv run stream temp Meter-run temperature measurements at the end of the prove-run.

Prv run stream press Meter-run pressure measurements at the end of the prove-run.

Prv run meter factor Meter Factor generated at the end of the prove-run.

Prv run CTLm Correction Factor for effect of temperature on fluid passing the meter-under-test.

Prv run CPLm Correction Factor for effect of pressure on fluid passing the meter-under-test.

Prv run CCFm Combined Correction Factor – for meter-run flow rates.

Prv run CorrMeterVol Meter-under-test Corrected Volume Rate– See page 16b.3 for calculations.

* Abbreviations: “Prv” = Prover, “ind” = indicated, “temp” = temperature, “press” = pressure, “Vol” = volume, “Corr” = corrected, “MUT” = Meter-under-test, “SUT” = Stream-under-test


Page 16b.24 7951 2510 (CH16b/AB)

16B.8 Prover Reporting The ‘Proving’ 7951 offers to printout a proving report at the end of a prover session. Alternatively, it can be printed on-demand by a making an appropriate selection from within the PRINTER (button) menu.

Master Meter report formats can be seen on pages 16b.25 and 16b.27.

16B.8.1 Print Requests using the front panel keyboard

(Ensure that an RS-232C port is configured for the connection to an ASCII compatible output device)


1. Press the grey PRINT-MENU button.

2. Navigate to this menu: <“Print report”>/<“Print”>.

3. Press the ‘b’ button.

4. Use the UP-ARROW button to scroll through the list of reports.

5. Press the ENTER button when “Prover report” appears on line two.


7951 2510 (CH16b/AB) Page 16b.25

Figure 16B.8.1: Format of Master Meter Printed Report - Volume

Master Meter Summary Report - Volume ------------------------------------

Prove report number: 24 Site location:Start time: 12/12/2001 09:09:10 Duration: 599.000 s =======================================================================Master Meter Details --------------------Serial number: Meter number:Prover Company:Prover Manufacturer:Prover model:Internal dia 200.000 mm Wall thickness 10.000 mm Meter material Modulus of E. 193053196000.000 N/m2 Meter expans coeff 0.000 PPM/Deg.C Cal temp. 20.000 Deg.C Flow rate 0.000 m3/hour=======================================================================Master Meter Run Data --------------------- Run1 Run2 Run3 Run4 Run5 (1) Pulses 10010.00 10017.00 10014.00 10063.00 10020.00 (2) K factor pulse/m3 168.000 168.000 168.000 168.000 168.000 (3) Ind vol/mass(1/2) m3 59.583 59.625 59.607 59.899 59.643 (4) Master temp Deg.C 15.000 15.000 15.000 15.000 15.000 (5) Master press bar abs 10.021 10.021 10.021 10.021 10.021 (6) Master MF 1.000 1.000 1.000 1.000 1.000 (7) CTLp 1.000 1.000 1.000 1.000 1.000 (8) CPLp 1.001 1.001 1.001 1.001 1.001 (9) CTSp 1.000 1.000 1.000 1.000 1.000 (10) CPSp 1.000 1.000 1.000 1.000 1.000 (11) CCFp (6*7*8*9*10) 1.001 1.001 1.001 1.001 1.001 (12) Corr prover vol 59.637 59.678 59.660 59.952 59.696 =======================================================================Meter Under Test ----------------Meter serial number 1 Meter number 1 Old K factor 168.000 pulse/m3, Old meter factor 1.015 Count repeatability 2.828 %, MF repeatability 3.063 % ManufacturerModelManufacturers flow calibration factor(s): _________________________________


Fluid Type: _________________________________

Density source: _________________________________

=======================================================================Meter Under Test Run Data ------------------------- Run1 Run2 Run3 Run4 Run5 (13) Interpolated Pulses 9889.977 10136.23 9983.726 9909.125 10019.99 (14) K factor pulse/m3 168.000 168.000 168.000 168.000 168.000 (15) Ind vol(13/14) m3 58.869 60.335 59.427 58.983 59.643 (16) Meter temp Deg.C 15.000 15.000 15.000 15.000 15.000 (17) Meter press bar abs 10.000 10.000 10.000 10.000 10.000 (18) CTLm 1.000 1.000 1.000 1.000 1.000 (19) CPLm 1.001 1.001 1.001 1.001 1.001 (20) CCFm (18*19) 1.001 1.001 1.001 1.001 1.001 (21) Corr meter vol(20*15) 58.916 60.383 59.474 59.030 59.690 (22) Meter Factor (12/21) 1.012 0.988 1.003 1.016 1.000 =======================================================================New meter factor 0.99862 New K factor (Old K factor / NewMF) 168.23184 MF deviation from previous (((max-min)/avg)*100) 1.596 %


Page 16b.26 7951 2510 (CH16b/AB)

Remarks: ________________________________________________________________________

________________________________________________________________________

Signature: Date: Company: ____________________ ______________ _____________________

Signature: Date: Company: ____________________ ______________ _____________________

Master Meter Run Data --------------------- Run6 Run7 Run8 Run9 Run10 (1) Pulses 10035.00 10020.00 10000.00 10000.00 10008.00 (2) K factor pulse/m3 168.000 168.000 168.000 168.000 168.000 (3) Ind vol/mass(1/2) m3 59.732 59.643 59.524 59.524 59.571 (4) Master temp Deg.C 15.000 15.000 15.000 15.000 15.000 (5) Master press bar abs 10.021 10.021 10.021 10.021 10.021 (6) Master MF 1.000 1.000 1.000 1.000 1.000 (7) CTLp 1.000 1.000 1.000 1.000 1.000 (8) CPLp 1.001 1.001 1.001 1.001 1.001 (9) CTSp 1.000 1.000 1.000 1.000 1.000 (10) CPSp 1.000 1.000 1.000 1.000 1.000 (11) CCFp (6*7*8*9*10) 1.001 1.001 1.001 1.001 1.001 (12) Corr prover vol 59.786 59.696 59.577 59.577 59.625 =======================================================================

Meter Under Test Run Data ------------------------- Run6 Run7 Run8 Run9 Run10 (13) Interpolated Pulses 10065.81 10173.66 10093.71 10031.65 10038.72 (14) K factor pulse/m3 168.000 168.000 168.000 168.000 168.000 (15) Ind vol(13/14) m3 59.916 60.558 60.082 59.712 59.754 (16) Meter temp Deg.C 15.000 15.000 15.000 15.000 15.000 (17) Meter press bar abs 10.000 10.000 10.000 10.000 10.000 (18) CTLm 1.000 1.000 1.000 1.000 1.000 (19) CPLm 1.001 1.001 1.001 1.001 1.001 (20) CCFm (18*19) 1.001 1.001 1.001 1.001 1.001 (21) Corr meter vol(20*15) 59.963 60.606 60.130 59.760 59.802 (22) Meter Factor (12/21) 0.997 0.985 0.991 0.997 0.997 =======================================================================


7951 2510 (CH16b/AB) Page 16b.27

Figure 16B.8.2 : Format of Master Meter Printed Report - Mass

Master Meter Summary Report - Mass ----------------------------------

Prove report number: 30 Site location:Prove start time: 13/12/2001 11:26:54 Duration: 599.000 s =======================================================================

Master Meter Details --------------------Serial number: Meter number:Prover Company:Prover Manufacturer:Prover model:Internal dia 200.000 mm Wall thickness 10.000 mm Meter material Modulus of E. 193053196000.000 N/m2 Meter expans coeff 0.000 PPM/Deg.C Cal temp. 20.000 Deg.C Flow rate 0.000 m3/s=======================================================================

Master Meter Run Data --------------------- Run1 Run2 Run3 Run4 Run5 (1) Pulses 10022.00 10011.00 10001.00 10012.00 10011.00 (2) K factor pulse/m3 168.000 168.000 168.000 168.000 168.000 (3) Ind mass/vol(1/2) m3 59.655 59.589 59.530 59.595 59.589 (4) Master temp Deg.C 15.000 15.000 15.000 15.000 15.000 (5) Master press bar abs 10.021 10.021 10.021 10.021 10.021 (6) Master MF 1.000 1.000 1.000 1.000 1.000 (7) CTSp 1.000 1.000 1.000 1.000 1.000 (8) CPSp 1.000 1.000 1.000 1.000 1.000 (9) CCFp (6*7*8) 1.000 1.000 1.000 1.000 1.000 (10) Corr prover mass 47148.14 47096.39 47049.34 47101.09 47096.39 =======================================================================

Meter Under Test ----------------Meter serial number 2 Meter number 2 Old K factor 0.213 pulse/kg, Old meter factor 1.003 Count repeatability 1.521 %, MF repeatability 1.541 % ManufacturerModelManufacturers flow calibration factor(s): _________________________________


Fluid Type: _________________________________

Density source: _________________________________

=======================================================================

Meter Under Test Run Data ------------------------- Run1 Run2 Run3 Run4 Run5 (11) Interpolated Pulses 10022.38 10011.00 10031.77 9981.538 10010.99 (12) K factor pulse/kg 0.213 0.213 0.213 0.213 0.213 (13) Ind mass(11/12) kg 47053.44 47000.01 47097.51 46861.68 46999.98 (14) Meter temp Deg.C 15.000 15.000 15.000 15.000 15.000 (15) Meter press bar abs 10.000 10.000 10.000 10.000 10.000 (16) Meter Factor (10/13) 1.002 1.002 0.999 1.005 1.002 =======================================================================New meter factor 0.99808 New K factor (Old K factor / NewMF) 0.21341 MF deviation from previous (((max-min)/avg)*100) 0.448 %

Remarks: ________________________________________________________________________



Page 16b.28 7951 2510 (CH16b/AB)

Master Meter Run Data --------------------- Run6 Run7 Run8 Run9 Run10 (1) Pulses 10025.00 10002.00 10016.00 10004.00 10010.00 (2) K factor pulse/m3 168.000 168.000 168.000 168.000 168.000 (3) Ind mass/vol(1/2) m3 59.673 59.536 59.619 59.548 59.583 (4) Master temp Deg.C 15.000 15.000 15.000 15.000 15.000 (5) Master press bar abs 10.021 10.021 10.021 10.021 10.021 (6) Master MF 1.000 1.000 1.000 1.000 1.000 (7) CTSp 1.000 1.000 1.000 1.000 1.000 (8) CPSp 1.000 1.000 1.000 1.000 1.000 (9) CCFp (6*7*8) 1.000 1.000 1.000 1.000 1.000 (10) Corr prover mass 47162.25 47054.05 47119.91 47063.46 47091.68 =======================================================================Meter Under Test Run Data ------------------------- Run6 Run7 Run8 Run9 Run10 (11) Interpolated Pulses 10086.64 10094.71 10046.46 10094.85 10134.50 (12) K factor pulse/kg 0.213 0.213 0.213 0.213 0.213 (13) Ind mass(11/12) kg 47355.13 47393.02 47166.49 47393.68 47579.83 (14) Meter temp Deg.C 15.000 15.000 15.000 15.000 15.000 (15) Meter press bar abs 10.000 10.000 10.000 10.000 10.000 (16) Meter Factor (10/13) 0.996 0.993 0.999 0.993 0.990 =======================================================================

Chapter 17 HART, SMART, and the 7951

7951 (Ch17/AE) Page 17.1

17. HART, SMART, and the 7951

17.1 What this Chapter tells you This Chapter is a comprehensive guide for understanding how the 7951 can be set-up for digital communications with “SMART” † type field transmitters.

Important Notice

This Chapter is only relevant to 7951’s with the “HART” add-on board installed. Contact us for up-to-date details of 7951 upgrade options.

17.2 Introduction to SMART and HART with the 7951 An extra I/O option‡ is required for the 7951 to communicate as a Current Input Device (Primary Master) on two separate two-wire 4-20mA loops of “SMART” field transmitters (Slaves).

Caution: Each HART loop must have no more than five “SMART” field transmitters connected at any one time. Exceeding this number will damage add-on boards.

The following “non-hazardous area only” diagram shows two HART loops with the maximum number of “SMART” field transmitters connected. In practice, far fewer transmitters are used.

Section 17.3 has details of external wiring involving the 7951.

HART Channel 2

HART Channel 1HART 1 Value0.125

Live

T1 T2 T3 T4 T5

T5T4T3T2T1

Caution: Connecting up “SMART” transducers has to be done with great care. Powering-up more than one point-to-point configured transmitter on a HART loop can produce an electrical current (20mA per transmitter) that can damage the 7951.

† A “SMART” transmitter is said to be intelligent because it contains a micro-processor that provides extra functionality. This may

take various forms, such as on-board calculations, handling multiple sensors, combining types of measurement. measurement integrity indicators, and so on. “SMART” is also used for the ability to re-use existing field wiring.

‡ See Appendix C for extra I/O options.

Chapter 17 HART, SMART and the 7951

7951 (Ch17/AE)Page 17.2

The communications standard for each loop is the HART§ Protocol**. A full technical discussion of this standard is outside the scope of this operating manual. There is a detailed discussion of the HART protocol in the Rosemount booklet entitled “HART Field Communications Protocol - A Technical Description”. However, particularly important aspects involving the 7951 are covered in later section as they are needed.

Application software is able to request data from dynamic variables that are kept and maintained by a “SMART” transmitter. These dynamic variables can be thought of as being very much like 7951-type data locations. Four dynamic variables per “SMART” field transmitter can be requested. A total of eight dynamic variables can be input to the 7951. Configuration details in this chapter concentrate on setting up the 7951to obtain up to eight (the maximum) measurement values.

HART 1

HART 3

HART 4

HART 2

HART 5

HART 6

HART 7

HART 8

Address = 1

HARTTransmitter

Primary

Secondary

Third

Fourth

Variables

Address = 9

HARTTransmitter

Primary

Secondary

Third

Fourth

Variables

HART network loop 2

Address = 1

HARTTransmitter

Primary

Secondary

Third

Fourth

Variables

Address = 8

HARTTransmitter

Primary

Secondary

Third

Fourth

Variables

7951HART Inputs

HART network loop 1

§ This is an acronym for “Highway Addressable Remote Transducer”. HART is a registered trademark of the HART

Communication foundation.** Implementation conforms to revision 5.5 of the HART protocol specification.


7951 (Ch17/AE) Page 17.3

17.3 Connecting the 7951 to a HART loop Warning: When installing field transmitters in hazardous areas, always follow wiring instructions provided by manufacturers of the field transmitters.

17.3.1 7951 electrical connections and impedance requirements

If the 7951 has the extra I/O option for HART, transmitter connections use Analog Inputs 5 and 6 for HART Loops 1 and 2 respectively.

“SMART” Analog Inputs on 7951 Klippon (Internally powered)

“SMART” Analog Inputs on 7951 D-type (Internally powered)

Every standard analog input on the 7951 utilises a internal 100 current sense resistor. The circuitry for the “SMART” analog inputs use a 100 current sense resistor in series with an active impedance. The total impedance is then sufficient for reliable operations at HART signal frequencies, while minimising the dc voltage drop across the 7951 terminals. This allows a sufficient voltage at the field transmitter even when powered through I.S. Barriers (or Isolators).

Parameter notes:

1. At dc, the voltage drop at the maximum current of 22mA is 3.4V 2. Minimum impedance in the HART extended frequency band (500 - 10khz) is 3303. Maximum impedance in the HART extended frequency band (500 - 10khz) is 480


7951 (Ch17/AE)Page 17.4

17.3.2 Frequency-shift buttoning

The HART protocol uses the American “Bell 202” standard frequency-shift buttoning (F.S.K.) method to mask a digital signal on to analog wiring.

Important Notice The “HART” extra I/O option can be used with the “Analog” extra I/O at the same time.This combination provides 2 off analog inputs 5 and 6. However, the F.S.K. signal produces random errors on the analog signal which affect the normal accuracy (See Appendix ‘C’).

We strongly recommend that analog inputs, being used for HART loop inputs, should only be used for HART communications.

17.3.3 Cable choice and the 65 s rule

There is a standard “65 s” rule that determines the maximum length of cable that can be used for reliable operation of the HART loop.

Step 1: Add up all the resistance in the network loop.

7951 current sense resistance; this is equivalent to 350 with the HART (extra I/O option). I.S. Barrier or Isolator. Cable.

Step 2: Find out the total cable capacitance

Step 3: Multiply the total resistance * total cable capacitance.

The resulting value must be less than 65 s.

We can provide multi-pair cable that has a maximum capacitance of 115 pF/m. The following table shows the recommended maximum cable lengths for typical HART network loops with this cable.

Table Notes: Cable length calculations take into account the 350

resistance from a 7951 with the HART option. It is assumed that a 150 I.S. Barrier has a

maximum end to end resistance of 185 It is assumed that a 300 I.S. Barrier has a

maximum end to end resistance of 340

A discussion of cable choices can be found in the Rosemount booklet entitled “HART Field Communications Protocol - A Technical Description”.

No. of slaves

Loopresistance

Max. Cable length

1 No Barrier 1171m 1 150 884m 1 300 713m 2 No Barrier 1136m 2 150 846m 2 300 673m 3 No Barrier 1101m 3 150 807m 3 300 633m 4 No Barrier 1067m 4 150 769m 4 300 593m 5 No Barrier 1032m 5 150 730m 5 300 553m


7951 (Ch17/AE) Page 17.5

17.4 Configuring the 7951 to use a HART loop This section shows the recommended approach to configuration of a 7951.

17.4.1 Configuring by using the software Wizard

Follow the step-by-step instructions for using a software Wizard to configure a 7951 that has the following set-up:

Example

A HART loop with one “SMART” static pressure field transmitter is attached to Analog Input 5. The objectives of this example are:

- To set a multi-drop address.

- To get static pressure from the fourth dynamic variable (on the transmitter) into the first HART menu data location dedicated to holding input values.

- To allocate the first HART input menu data location to the Line pressure calculation.

Go to the Wizardselection menu

1. Press the MENU button so that page 1 of the main menu appears.

2. Use the DOWN-ARROW button until the “Configure” main menu option is displayed.

3. Press the lettered-button that is alongside “Configure”.

4. Press the blue ‘a’ button twice.

Select the HART Wizard

5. Press the ‘b’ button, and then use the DOWN-ARROW button to scroll through a list of Wizards.

6. Press the ‘b’ button when “Hart inputs” appears on the display.

Select the 7951“HART” data location

7. Press the ‘d’ button to answer “yes” to the prompt.

Choose the HART Loop

8. Parameter <”HART 1 PhyLinkNo“> shows “HART link 1” by default. This example involves HART Loop 1 (HART link 1) so there maybe no need to change the setting.

However, if anything other than “HART link 1” is shown:

Press the ‘b’ button and then use the DOWN-ARROW button to scroll through the options.

Press the ‘b’ button when “HART link 1” is displayed.

9. Press the ENTER button to continue to the next step of the Wizard.

Choose the address of the “Field transmitter”

10. Press the ‘b’ button.

11. Use the DOWN-ARROW button to scroll through the options until “HART address 5” is shown.

12. Press the ‘b’ button to confirm this selection.



7951 (Ch17/AE)Page 17.6

Choose the fourth dynamic variable


15. Use the DOWN-ARROW button to scroll through the options until “Fourth variable” is shown.

16. Press the ‘b’ button to confirm this selection


Choose the type of dynamic variable


19. Use the DOWN-ARROW button to scroll through the options until “Static press (G)” is shown.

20. Press the ‘b’ button to confirm this selection.


Put the field transmitter on-line


23. Use the DOWN-ARROW button to scroll through the options until “On line” is shown.

24. Press the ‘b’ button to confirm this selection

25. Press the ENTER button to continue to the next step of the wizard.

Monitor the response from issuing the on-line/off-linecommand

26. Watch the response message. It should cycle from “None” to “Configured” in less than a minute. Note: The response of “SMART error” may appear if there is there is a problem with the HART loop.

27. Press the ENTER button to continue to the next step of the wizard.

Change status to get live values from the field transmitter

28. Press the ‘d’ button.

29. Use the DOWN-ARROW button to scroll through the options until “Live” is shown.

30. Press the ‘b’ button to confirm this selection. Live static pressure values (gauge units) should now be displayed.


Skip remaining questions

32. Press the ‘c’ button to answer “no” to the prompt.

33. Repeat step 32 until the Wizard is completed.

Allocate the HART data input location.

34. Use the “Pressure” Wizard to make parameter <”HART input value 1“> the source for Pressure measurements.


7951 (Ch17/AE) Page 17.7

17.5 Post configuration - viewing HART data This sub-section provides a complete check-list of all the parameters associated with checking information returning from HART loops.

Task 1: Checking the results

Step 1: Find this menu: <“Health check”>/<”HART Inputs”>

Step 2: Look at data shown in this check-list


HART input 1 value HART input 2 value HART input 3 value HART input 4 value Values from eight dynamic variables HART input 5 value HART input 6 value HART input 7 value HART input 8 value

HART software ver HART board firmware identification.

HART no. of phy links This shows the number of HART network loops. Default setting is “None”

HART status This shows a digit for each of the eight HART data inputs: Digit = ‘0’ - Input is not configured (not in use) Digit = ‘1’ - Input is configured (in use) Digit = ‘2’ - Input configuration failed due to an error Default state is 00000000

17.6 SMART units of measurement Support is provided for a sub-set of the SMART units of measurement.

Temperature Density Pressure Mass rate

1. Deg.C. 1. g/cc 1. In WG 1. g/sec

2. Deg.F 2. g/m3 2. mm WG 2. g/Min

3. Kelvin 3. lb/gallon (UK) 3. Bar 3. h/Hour

4. lb/ft3 4. mBar 4. Kg/sec

5. Kg/litre 5. Pa 5. Kg/Min

6. g/litre 6. MPa 6. Kg/day

7. lb/in3 7. In HG 7. Tonnes/Min

8. Tonnes/Hour

9. Tonnes/Day

10. Lb/sec

11. Lb/Hour

12. Lb/Day

Note: Values received in unsupported measurement units are displayed without units of measurement - line 3 of the display is left blank. However, calculations that use this data always assume the default units of measurement. For temperature data, this would be Deg.C”.


7951 (Ch17/AE)Page 17.8

7951 2510 (Ch18/AD) Page 18.1

18. BATCHING (TRANSACTIONS) This chapter explores the 7951 support for Standard Batch Operations and optional Retrospective Calculations.

18.1 Standard Batch Operations Batch operations comprise transactions and recording of product transfers and conditions over a defined period. The records kept are the current transaction in progress and the previous (last) completed transaction. Additionally, the transaction can be archived. Both the current and previous records may be printed out on-demand or automatically on transaction completion. The archived transaction maybe viewed or printed later when required.

These records are called ‘Batch Transaction Records’ but may sometimes be referred to as ‘Quantity Transaction Records’ (QTR) and typically contain the normal totalisers, start/stop time/date and conditions, together with weighted averages.

18.1.1 Batch Operation Types The Flow Computer offers 4 types of batch operation:

(1) DailyThis type of batch commences at a programmed (SET) hour – known as the contract hour. The duration is 24 hours at all times, unless the calendar clock is adjusted. Batches are back-to-back and therefore have to be halted on-demand by a menu-based command selection.

(2) TimedThis type of batch commences when a programmed (SET) date and time matches that of the Flow Computer calendar clock. Time is the primary parameter for completing a batch. The duration of a batch is a fixed, user-programmed period. Batches are always back-to-back and have to be halted on-demand by a menu-based command selection or by the F1 button.

(3) Manual TriggerThis type of batch is started by selecting a menu ‘command’. User- intervention is the essential parameter for completing a batch. The duration of a batch is therefore entirely dependent on when the “Halt” command is selected. Batches are not back-to-back unless commands are issued in quick succession.

Alternatively, the F1 front panel button can start and stop a batch.

(4) Programmed QuantityThis type of batch is more sophisticated than previous types. A chain of 6 back-to-back batches can be set-up, each batch with parameters for programming the quantity to deliver, optional delivery rate, and start method. The chain can be linked such that it is continuously repeated.

An individual quantity-based batch transaction can commence either by: Menu-based command selection, Starting at a pre-set date and time, or Starting immediately after being enabled.

This type is more sophisticated than the previously mentioned types. A chain of 6 back-to-back batches can be set-up, each batch with parameters for programming the quantity to deliver, the optional delivery rate and start method. The chain can be linked such that it is continuously repeated.

Product flow is the essential parameter for completing a batch. The batch is complete when a pre-set quantity of the measured product has been delivered – quantity is in terms of mass flow, gross volume flow or net volume flow.

Chapter 18 Batch Operations

Page 18.2 7951 2510 (Ch18/AD)

Simple flow control is available by means of automatically opening and closing a stream block valve at the start and end of a quantity batch. The subject of “Valve Control and Monitoring” is dealt with in Chapter 16 – some configuration is required.

An alternative option is for the 7951 Flow Computer to continuously control the rate of product flow, thus giving a more precise delivery of the product during each batch transaction. Flow Delivery Control (FDC) features an auto-configured PID algorithm that can manipulate a proportionally controlled valve1. After a flow-controlled batch is underway, the user can adjust the deliverable quantity, abort batches, or pause/resume the batch. System alarms flag events, such as completion or approaching end of batch.

Table 18.1: Availability of Optional Features

Batch Type Pause/Resume? Qty Adjustment? Over-spill limit?

Daily No No No Timed No No No Manual No No No

Quantity (FDC) Yes Yes Yes Quantity (w/o FDC) No No No

Abbreviation used: “FDC” = Flow Delivery Control, “w/o” = without

1 The Flow Control Valve is expected to be independent of the valves used during a proving session.


7951 2510 (Ch18/AD) Page 18.3

18.1.2 Batch Operation Parameter Reference This section is a reference for all the parameters associated with batch transaction operations.

Points To Observe1. Only one type of batch operation

can operate at any one time. A batch type is exclusively selected at that moment of being enabling by a menu-based command e.g. “Run”. This action also halts an existing batch transaction.

2. There are menu system areasfor viewing the records of theprevious and current batch transactions.(Menu: <“Batching”>)

3. The transaction record of a completed batch is automatically archived. (See “Archiving” section in Chapter 9).

Menu Navigation List: (1) <“Configure”>/<“Batching”> and (2) <“Batching”>

Parameter List (1 of 2): * shows data that can be “Live” or “Set”


1 Batch start time 24 Flow ramp limit (M) 2 Timed batch duration 25 Trickle flow rate (M) 3 Batch time enable H, J 26 Meter run max flow (M) 4 Manual batch enable H, J 27 Daily contract hour 5 Qty unit-type select A 28 Daily batch enable H, J 6 Qty batch enable H, I, J 29 Batch auto print L 7 Qty batch pause G 30 Meter density *8 Batch status 31 Base density *9 Batch qty delivered E 32 Degrees API *

10 Batch qty remaining E 33 Meter factor *11 Starting program ID 34 Flowmeter K factor *12 Current program ID 34 BS&W value *13 Batch manual trigger K 35 CTL 14 Adjust batch qty L 36 CPL 15 Modified batch qty (L) 37 Meter temperature *16 Prog1 quantity 38 Meter pressure *17 Prog1 flow rate 39 Base density oil 18 Prog1 start type 40 Degrees API oil 19 Prog1 start time 41 Meter kinematic visc * 20 Prog1 name - Flow status (F) 21 Prog1 next program D - Operating mode B 22 Qty overrun limit F 23 PID flow control (E),M, Q

Associated notes follow the parameter list. (X) - Mentioned in note X

Figure 18.1: Batching Operation Parameters


Page 18.4 7951 2510 (Ch18/AD)

Parameter List (2 of 2): * shows data that can be “Live” or “Set” Index Parameters Notes? Index Parameters Notes?

CURRENT BATCH TRANSACTION RECORD PREVIOUS BATCH TRANSACTION RECORD 42a Batch ticket number O 42b Batch ticket number O 43a Batch status 43b Batch status 44a Product name R 44b Product name 45a Program name 45b Program name 46a Batch start time C: 7 46b Batch start time 47a Start meter temp C: 2 47b Start meter temp 48a Start meter press C: 3 48b Start meter press 49a Start meter dens C: 8 49b Start meter dens 50a Start IV total C: 1 50b Start IV total 51a Start GV total C: 1 51b Start GV total 52a Start ISV total C: 1 52b Start ISV total 53a Start GSV total C: 1 53b Start GSV total 54a Start mass total C: 1 54b Start mass total 55a Start NV oil total C: 1 55b Start NV oil total 56a Start NSV oil total C: 1 56b Start NSV oil total 57a Start NM oil total C: 1 57b Start NM oil total 58a Start NV water total C: 1 58b Start NV water total 59a Start NSV water tot C: 1 59b Start NSV water tot 60a Start NM water total C: 1 60b Start NM water total 61a Ind vol total C: 1 61b Ind vol total 62a Gross vol total C: 1 62b Gross vol total 63a Ind std vol total C: 1 63b Ind std vol total 64a Gross std vol total C: 1 64b Gross std vol total 65a Mass total C: 1 65b Mass total 66a Oil vol total C: 1 66b Oil vol total 67a Oil std vol total C: 1 67b Oil std vol total 68a Oil mass total C: 1 68b Oil mass total 69a Water vol total C: 1 69b Water vol total 70a Water std vol total C: 1 70b Water std vol total 71a Water mass total C: 1 71b Water mass total 72a Alarm total C: 1 72b Alarm total 73a Flowmeter errors C:11 73b Flowmeter errors 74a Current IV total C: 1 74b Close IV total 75a Current GV total C: 1 75b Close GV total 76a Current ISV total C: 1 76b Close ISV total 77a Current GSV total C: 1 77b Close GSV total 78a Current mass total C: 1 78b Close mass total 79a Current NV oil total C: 1 79b Close NV oil total 80a Current NSV oil tot C: 1 80b Close NSV oil tot 81a Current NM oil total C: 1 81b Close NM oil total 82a Current NV water tot C: 1 82b Close NV water tot 83a Current NSV water total C: 1 83b Close NSV water total 84a Current NM water tot C: 1 84b Close NM water tot 85a Batch av temp C: 2 85b Batch av temp 86a Batch av press C: 3 86b Batch av press 87a Batch av meter dens C: 8 87b Batch av meter dens 88a Batch av base dens C: 9 88b Batch av base dens 89a Batch av degrees API C:10 89b Batch av degrees API 90a Batch av kine visc C:12 90b Batch av kine visc 91a Batch av MF C:11 91b Batch av MF 92a Batch av K factor C:11 92b Batch av K factor 93a Batch av base BS&W C: 5 93b Batch av base BS&W 94a Batch av BS&W C: 5 94b Batch av BS&W 95a Batch av CSW 95b Batch av CSW 96a Batch av CTL C: 4 96b Batch av CTL 97a Batch av CPL C: 4 97b Batch av CPL 98a Batch av oil bdens C: 6 98b Batch av oil bdens 99a Batch av oil deg API C: 6 99b Batch av oil deg API

100a Current date/time C: 7 100b Batch end date/time 101a Current meter temp C: 1 101b Batch end meter temp 102a Current meter pres C: 2 102b Batch end meter pres 103a Current meter dens C: 8 103b Batch end meter dens

“IV” = Indicated Volume, “ISV” = Indicated Standard Volume, “GV” = Gross Volume, “GSV” = Gross Standard Volume, “NV” = Net Volume, “NSV” = Net Standard Volume, “NM” = Net Mass, “av” = average, “dens” = density, “pres” = pressure


7951 2510 (Ch18/AD) Page 18.5

Notes:A By default, gross volume is the selected unit of measurement for monitoring product flow during a quantity-

based batch transaction. Alternative units of measurement for selection are net volume and mass.

B Batch transactions require the 7951 Flow Computer to be operating in “Normal” mode. [‘i’ button menu]

C:<n> Use Table 18.2 to help identify the initial data source for batch transaction record parameters

Table 18.2: Batch Transaction Record - Parameter Source Reference

Ref. No. Source Category

1 Normal mode (Main/Standard) total 2 Metering Temperature 3 Metering Pressure 4 API Referral 5 % Water (by Standard Volume) 6 Net Oil/’Water’ Calculations 7 7951 Calendar Clock 8 Metering density 9 Base density

10 API Degrees 11 Flow Metering 12 Viscosity

D This is for chaining one batch transaction program to another batch transaction program. The “None” option is for ending the chain.

E Due to the mechanics of batching, the delivered quantity may exceed the pre-set quantity. However, this over-spill can be minimised by using the Flow Delivery Control option. Over-spill is not filtered out of batch records. (Also, see Note F)

Over-spill due to 7951 Flow Computer timing is minimised to the delay from the method of recording values at some time during a machine cycle.

F Limit alarm threshold for monitoring the over-spill of a batch. An over-spill outside the (upper) limit will raise a “Qty batch overrun” alarm. It can be cleared when there the batch is completed and there is a ‘flow stop’ state.

This alarm limit check will not operate unless Flow Delivery Control is active and the programmed threshold is greater than zero.

(Also, see Note E)

G Pause and resume controls are available when running a quantity-based batch transaction with active Flow Delivery Control. The “pause” ‘command’ allows a live adjustment to the deliverable quantity. Adjustments take effect immediately upon resumption of the batch. (See Table 18.1 for availability of other batch features)

H Activating another batch type will immediately terminate all existing batch activities. There are termination exceptions:

A quantity batch cannot be stopped without using the “halt” ‘command’ (of <“Qty batch enable”>). Otherwise, attempts to enable another batch type will fail and result in a “Qty batch running” INFO class system alarm. This INFO alarm can be accepted and cleared at any time.

A quantity batch (with active Flow Delivery Control) cannot be enabled unless the Flow Computer is in a ‘flow stopped’ state. Otherwise, attempts will fail and result in a “Qty batch start F” INFO class system alarm. This alarm can be accepted and cleared at any time.


Page 18.6 7951 2510 (Ch18/AD)

I A quantity batch with a manual trigger must first be enabled with <“Qty batch enable”> and then triggered by <“Batch manual trigger”>. Further triggering may be needed if other chained programs use a manual start.

J Terminating a running batch will leave both current and previous batch records with identical values until a new batch is started.

K Target flow rate for achieving the “maintain” state during a quantity batch. This parameter is not applicable unless using the FDC (Flow Delivery Control) feature. (See Table 18.1 for availability of FDC)

L Enable or prevent an automatic printout of the batch report immediately on completion of a batch. A serial communication port will need to be configured for a connection to an ASCII compatible printer.

M A quantity type batch can use the 7951 software based PID algorithm to manipulate a proportional valve and therefore control the product delivery rate.

The “PID” option for this parameter will auto-configure most PID parameters apart from the gain, the integral and the derivative. (See “PID” reference pages in Chapter 9)

Associated Flow Delivery Control Parameters:

<“Trickle flow rate”> This will specify the minimum flow rate for the automated closing stage of a batch. A default value of 0 forces the 7951 to assume the ‘trickle’ is 2% of the

value programmed (SET) for <“Meter run max flow “>.

<“Flow ramp limit”> This will override the limit that appears within the PID configuration menu.

<“Meter run max flow”> This is a capping limit for the rate of flow.

The “Simple open & close” option for this parameter will cause the Flow Computer to open both the Stream Block Valve and the Flow Control Valve at the start of a batch, and close them both at the end of the batch. With this option there is no control over the product delivery rate.

The “Off” option for this parameter is for when the Flow Computer does not control valves.

N Pause a quantity-based batch, SET a new deliverable quantity and then resume the batch. (Requires FDC.)

O This parameter cannot be reset to zero on-demand but will rollover to zero after exceeding 4.95 billion.

P Weighted averaging uses the Gross Volume flow rate.

Q If using PID Control (Flow Delivery Control) or the ‘simple open and close’ method, it is necessary for the Flow Computer to auto-control valves. Set-up details are as guided in the “Valve Control and Monitoring” section of Chapter 16A.

It is also necessary to select a pre-built map of status I/O assignments – maps are listed in Chapter 16. To check on and select an I/O assignment:

Navigate to this menu: <”Configure”>/<”Prover”>/<”Common prv details”>. Locate the <prover I/O assignment> (or similar) parameter and edit as necessary.

R For details, turn to the “Interface Detection” reference pages in Chapter 11.


7951 2510 (Ch18/AD) Page 18.7

18.1.3 Guided Example 1: Manual Trigger Type Batch

This example demonstrates how a manually triggered type is configured, commenced by a menu-based ‘command’ and completed on-demand by another ‘command’. Adapt the example to be applicable to your installation.

What to do:Read the Overview and then browse through the Operation Events list and associated parameter list for this example.

Overview:Figure 18.2 gives a graphical overview for the example. It shows single-shot batches, each varying in duration and, consequently, the quantity delivered. They are totally unaffected by the flow conditions, which are reasonably stable in this case. The Flow Computer does not control product flow.

Figure 18.2: Manual Triggered Batch Type

Operation Events:

1. Flow rate increases independently of Flow Computer.

2. Operator uses the “Run” command when flow rate is adequate. Batch B1 starts immediately, with the batch status changing to “In progress”

3. Batch B1 continues and product flow remains stable until ‘Tank A’ approaches full capacity.

4. Flow rate decreases independently of Flow Computer.

5. Batch B1 completes when the operator selects the “Halt” command. The batch status then changes from “In progress” to “Complete”.

6. Batch B2 does not start yet. There is a wait until ‘Tank B’ is ready.

7. Flow rate increases independently of Flow Computer.

8. Operator uses the “Run” command when flow rate is adequate. Batch B2 starts immediately, with the batch status changing to “In progress”

9. Batch B2 continues and product flow remains stable until ‘Tank B’ approaches full capacity.

10. Flow rate decreases independently of Flow Computer.

11. Batch B2 completes when the operator selects the “Halt” command.

Associated Parameter List: (The menu navigation list is on page 18.3)


Manual batch enable * “Run” Command for enabling and triggering batch Batch status ** (See “Operation Events”) Useful for monitoring the batch operation.

* “Halt” option is the command for completing a batch and also deselecting the batch type ** Viewed from within the current batch transaction record


Page 18.8 7951 2510 (Ch18/AD)

18.1.4 Guided Example 2: Timed Batches

This example demonstrates how the timed batch type is configured, commenced at a programmed date and time, and halted on-demand. Adapt the example to be applicable to your installation.

What to do: Read the Overview and then browse through the Operation Events list for this example.

Overview:Figure 18.3 gives a graphical overview for the example. It shows a series of back-to-back batches, each programmed to last 300 seconds. The first batch commences - triggers - when the 7951 calendar clock matches a programmed (SET) date and time, “12-03-2002 08:00:00”. Timed batch operations are totally unaffected by the flow conditions, which are reasonably stable in this case. Batch Bn is interrupted 200 seconds after starting, following the selection of a “halt” command.

Figure 18.3: Timed Batches

Operation Events:1. Configure associated parameters in the order as listed in the table below.

2. Wait for the 7951 calendar clock to match the trigger date and time.

3. Trigger occurs on 12th March 2002 at 8 o’clock in the morning. Batch B1 starts immediately.

4. Batch B1 completes after 300 seconds and batch B2 starts immediately.

5. Batch B2 completes after a further 300 seconds and batch B3 starts immediately.

6. Batch B3 completes after a further 300 seconds.

7. Batches continue …

8. Later on, batch Bn starts.

9. After 200 seconds, the “halt” command is selected. Batch Bn ends immediately but it is still considered to be complete - the batch status shows “complete”.

10. To resume this timed batch operation, program a new date and time, adjust the duration if necessary and then re-select the “Run” command.



Timed batch duration 300.0 (s) 300 seconds per batch. Batch time enable “Run” Command for enabling the timed batch type. Batch start time * 12-03-2002 08:00:00 Trigger for 1st.batch is 12th March 2002 at 8am. Batch status ** In Progress Compete Useful for monitoring the general batch operation

* “00-00-0000 00:00:00” = Start 1st batch immediately after editing duration and using “Run” command ** Viewed from within the current batch transaction record

Configuration Option:The date element of <”Batch start time“> is optional. It can be “00-00-00” if commencing with the first batch on the present day. The time element must always be specified since “00:00:00” is midnight.


7951 2510 (Ch18/AD) Page 18.9

18.1.5 Guided Example 3: Quantity Batch with FDC - Single Program Loop

This example demonstrates how a quantity batch program can be chained to itself such that it is continually repeated until halted on-demand.


Overview:Figure 18.4 gives a graphical overview for the example. It shows the same quantity batch program (BP1)repeated twice. Batch program BP1 is configured with various details (see Table 18.3), including a requirement to start the batch transaction with a command.

The first batch transaction is started by the “Run” (manual trigger) command whilst the Flow Computer is in a ‘flow stopped state’. Flow Delivery Control is then responsible for delivering the pre-set quantity, with minimal over-spill, and ending the batch. The duration of this batch transaction can vary and this is due to varying flow conditions.

After the first batch transaction is complete, quantity-type batching remains enabled. The subsequent batch transaction (batch program BP1) is triggered manually by the operator at a convenient time.

The batch can be repeated any number of times until the “halt” (enable/disable) command is selected, when no more quantity batching is needed.

Directly associated parameters are listed in Table 18.3 on page 18.10. All other parameters, such as the Gross Volume flow rate, are identifiable from the reference information in Section 18.1.2.

Figure 18.4: Quantity Batch with FDC - Repeated Program

Operation Events:1. Quantity batch operation type enabled when the “Run” (enable/disable) command is selected.

2. Flow is reduced by some means - on-line or off-line valve control - and falls below the programmed (SET) ‘flow stop’ threshold. The Flow Computer is then in a ‘flow stopped’ state.

3. The first batch (BP1) starts immediately when the “Run” (manual trigger) command is selected.

4. Flow Delivery Control increases flow to match the programmed target rate (in batch program ‘1’)

5. Flow Delivery Control maintains flow at the target rate until 98% of the pre-set quantity is delivered

6. Flow Delivery Control decreases flow to match the programmed trickle rate (in batch program ‘1’)

7. Batch stops when all the pre-set quantity is delivered. Quantity batch status displays “Idle”.


Page 18.10 7951 2510 (Ch18/AD)

(Operation Events continued…)

8. The second batch (BP1) starts immediately when the “Run” (manual trigger) command is selected.

9. Flow Delivery Control increases flow to match the programmed target rate (in batch program ‘1’).

10. Flow Delivery Control maintains flow at the target rate until 98% of the pre-set quantity is delivered.

11. Flow Delivery Control decreases flow to match the programmed trickle rate (in batch program ‘1’).

12. Batch stops when all the pre-set quantity is delivered.

13. Quantity type batching is deactivated (disabled) by selecting a “halt” (enable/disable) command.

Table 18.3: Directly Associated Parameter List (of Example 3)


Qty unit-type select (Any “volume” option) Either “Gross Volume” or “Net Volume” PID flow control “PID” Activate Flow Delivery Control (FDC) Flow ramp limit 100% FDC Parameter: 100% = Allow any ramp-up rate Trickle flow rate 120 m3/hour FDC Parameter: Minimum flow rate for end of batch.

Meter run max flow 400 m3/hour FDC Parameter: Maximum flow rate at any time Oty overrun limit 0 m3 0 = No over-spill limit check

Starting program ID “Program 1” Chain begins with Batch Program ‘1’ Prog1 quantity 1000 m3 Deliverable quantity excluding adjustments and over-spill. Prog1 flow rate 200 m3/hour Target rate to be maintained by FDC for majority of batch. Prog1 start type “Manual start” Manual trigger required.

Prog1 name “Test Prog 1” Free-form text of up to 20 characters. Prog1 next program “Program 1” Chain ends with Batch Program ‘1’. This forms the loop.

Qty batch enable “Run” Enable the batch operation type. (1st. batch requires trigger)

Batch manual trigger * “Run” The Trigger for each programmed manual batch Batch status ** In Progress Compete Useful for monitoring the general batch operationBatch status *** (See Operation Events) Useful for monitoring the quantity batch operation

Batch qty delivered (Increasing as delivered) Useful for monitoring the quantity batch operation Batch qty remaining (Decreasing as delivered) Useful for monitoring the quantity batch operation

* ‘Halt’ option is the command for stopping the program loop ** Viewed from within the current batch transaction record *** Viewed from within the “Batching” configuration menu


7951 2510 (Ch18/AD) Page 18.11

18.1.6 Guided Example 4: Quantity Batch with FDC - Pause and Resume Controls

This example demonstrates how a batch can be paused for a period and then resumed.


Overview:Figure 18.5 gives a graphical overview of this example. It shows a single-shot quantity batch (BP2) that is paused mid-way for a period of time ‘tI’ and then resumed until the pre-set quantity is delivered.

Batch program BP1 is configured with various details (see Table 18.4), including a requirement to start the batch transaction with a command. The duration of this batch transaction can vary due to varying flow conditions.

Directly associated parameters are listed in Table 18.4 on page 18.12. All other parameters, such as the Gross Volume flow rate, are identifiable from the reference information in Section 18.1.2.

Figure 18.5: Quantity Type Batch with FDC - Pause/Resume Control

Operating Events:

1. Quantity batch operation type enabled when the ‘Run’ (enable/disable) command is selected,

2. Flow is reduced by some means - on-line or off-line valve control - and falls below the programmed (SET) ‘flow stop’ threshold. The 7951 Flow Computer is then in a ‘flow stopped’ state,

3. Batch BP2 starts immediately when the ‘Run’ (manual trigger) command is selected,

4. Flow Delivery Control increases flow to match the programmed target rate (from batch program ‘2’),

5. Flow Delivery Control maintains flow at the target rate until the ‘Pause’ command is selected,

6. Flow Delivery Control decreases flow to achieve a ‘flow stopped’ state,

7. Batch BP2 resumes when the ‘Resume’ command is selected,

8. Flow Delivery Control increases flow to match the programmed target rate (of batch program ‘2’),

9. Flow Delivery Control maintains flow at the target rate until 98% of the pre-set quantity is delivered,

10. Flow Delivery Control decreases flow to match the programmed trickle rate (of batch program ‘2’),

11. Batch BP2 stops when all the pre-set quantity is delivered,

12. Quantity type batching is deactivated (disabled) by selecting a ‘halt’ (enable/disable) command,


Page 18.12 7951 2510 (Ch18/AD)

Table 18.4: Directly Associated Parameters (for Example 4)


Qty unit-type select (Any “volume” option) Either Gross Volume or Net Volume units of measurement PID flow control “PID” Activate Flow Delivery Control (FDC) Flow ramp limit 100% FDC Parameter: 100% = Allow any ramp-up rate Trickle flow rate 120 m3/hour FDC Parameter: Minimum flow rate for end of batch.

Meter run max flow 500 m3/hour FDC Parameter: Maximum flow rate at any time Oty overrun limit 0 m3 0 = No over-spill limit check

Starting program ID “Program 2” Chain begins with Batch Program ‘1’ Prog2 quantity 1500 m3 Deliverable quantity excluding adjustments and over-spill Prog2 flow rate 400 m3/hour Target rate to be maintained by FDC for majority of batch Prog2 start type “Manual start” Manual trigger required

Prog2 name “Test Prog 2” Free-form text of up to 20 characters Prog2 next program “None” No more links in this batch program chain

Qty batch enable “Run” Command for enabling the quantity batch type Batch manual trigger * “Run” The trigger command for a programmed manual batch

Qty batch enable “Pause” “Resume” Pause/Resume commands for mid-way through batch Batch status ** “In Progress” “Compete” Useful for monitoring the general batch operationBatch status *** (See Figure 18.5) Useful for monitoring the quantity batch operation

Batch qty delivered 0 1500 + Over-spill Useful for monitoring the quantity batch operation Batch qty remaining 1500 0 Useful for monitoring the quantity batch operation

* “Halt” option is the command for stopping the program loop ** Viewed from within the current batch transaction record *** Viewed from within the “Batching” configuration menu


7951 2510 (Ch18/AD) Page 18.13

18.1.7 Guided Example 5: Daily Batch This example demonstrates how the daily batch operates.


Overview:Figure 18.6 gives a graphical overview of this example. It shows two back-to-back batches, each batch lasting 24 hours. The first 24-hour batch B1 commences - triggers - when the “Run” command is selected. The batch operation is totally unaffected by the flow conditions, which are reasonably stable in this case. Batch B1 ends automatically after 24 hours has elapsed. The second batch B2 then commences automatically. Batch B2 ends automatically after 24 hours has elapsed. However, this time a “Halt” command is selected by the operator and prevents more batches.

Figure 18.6: Daily Batch

Operation Events:

1. Flow rate is controlled independently of Flow Computer.

2. Operator uses the “Run” command when flow rate is adequate. Batch B1 starts immediately, with the batch status changing to “In progress”.

3. Batch B1 continues and product flow remains stable until 24 hours have elapsed.

4. Batch B2 commences immediately without any operator intervention.

5. Batch B2 completes after 24 hours have elapsed.

6. Operator selects the “Halt” command at the same time that the batch completes.

7. The batch status then changes from “In progress” to “Complete”.



Daily contract hour “0800” Select “0800” as contract hour. Control “Run” Command for starting the 24-hour batches. Control “Halt” Command for stopping the 24-hour batches


Page 18.14 7951 2510 (Ch18/AD)

18.1.8 Printing Batch Reports

Batch reports can output by using one of several methods:

1. Method: On-demand This feature requires no configuration apart from setting up an RS232C port, as guided in Chapter 7.

To activate, press the PRINT-MENU button and then select the “Print report” menu option. Now choose a report by selecting from the multiple-choice options. Table 18.5 shows the relevant options for the batch reports. The report format can be seen on pages 18.15 and 18.16.

Table 18.5: Descriptors for Printed Batch Reports


“Current batch” Printout the “Current” batch (transaction) record in a report format “Previous batch” Printout the “Previous” batch (transaction) record in a report format

2. Method: Automatic Printed Report The Flow Computer can be configured to automatically printout a report on completion of a batch transaction.

Activation instructions:

1. Navigate to this menu: <”Configure”><”Batching”>/<”Batch report print”>

2. Select the “On” option

All methods require a RS232C communications port to be set-up for connection to a printer or other ASCII compatible output device. Printed reports are transmitted in an ASCII format through the port configured exclusively for this type of connection.

When a batch report is first printed, it is stamped with “ORIGINAL”. All subsequent printouts of the same report will be stamped with “DUPLICATE”. However, the “current” batch report is stamped with “DUPLICATE” only if the report values have not changed.


7951 2510 (Ch18/AD) Page 18.15

Figure 18.7: "Current Batch" Printed Report

BATCH TRANSACTION RECORD ========================

Operators signature: ............. Report printing time: XX/XX/XXXX XX:XX:XX Original/duplicate XXXXXXXXX

Tag number XXXXXXXXXXXXXXXXX Batch ticket number X Batch revision X Previous revision X

Batch status XXXXXXXXXX Product name XXXXXXXXXXXXXXXXX Program name XXXXXXXXXXXXXXXXX

Batch base temp X.XXX Deg.C Batch base pressure X.XXX bar abs Batch equilib press X.XXX bar abs

Batch open/close parametersBatch start time XX/XX/XX XX:XX:XX Current date/time XX/XX/XX XX:XX:XX Start meter temp X.XXX Deg.C Current meter temp X.XXX Deg.C Start meter press X.XXX bar abs Current meter pres X.XXX bar abs Start meter dens X.XXX g/cc Current meter dens X.XXX g/cc

Batch open/close Cumulative Totals----------------------------------Start IV total X.XXX m3 Current IV total X.XXX m3 Start GV total X.XXX m3 Current GV total X.XXX m3 Start ISV total X.XXX std m3 Current ISV total X.XXX std m3 Start GSV total X.XXX std m3 Current GSV total X.XXX std m3 Start mass total X.XXX kg Current mass total X.XXX kg

Batch TotalsInd vol total X.XXX m3 Gross vol total X.XXX m3 Ind std vol total X.XXX std m3 Gross std vol total X.XXX std m3 Mass total X.XXX kg Alarm total X.XXX Flowmeter errors X.XXX

Quantity Batch DetailsBatch program ID XXXXXXXXXX Batch request qty X.XXX m3 Modified batch qty X.XXX m3

Weighted AveragesBatch av temp X.XXX Deg.C Batch av press X.XXX bar abs Batch av meter dens X.XXX kg/m3 Batch av base dens X.XXX kg/m3 Batch av degrees API X.XXX Batch av kine visc X.XXX cSt Batch av MF X.XXX Batch av K factor X.XXX pulse/m3 Batch av CTL X.XXX Batch av CPL X.XXX Batch av CCF X.XXX Batch av base BS&W X.XXX % Batch av BS&W X.XXX % Batch av CSW X.XXX Batch av oil bdens X.XXX kg/m3 Batch av oil deg API X.XXX Batch av water bdens X.XXX kg/m3

Alarm CountsAlarms during batch X If alarm count is not zero, refer to alarm history log to obtain alarm details.


Page 18.16 7951 2510 (Ch18/AD)

Figure 18.8: "Previous Batch" Printed Report

BATCH TRANSACTION RECORD ========================

Operators signature: ............. Report printing time: XX/XX/XXXX XX:XX:XX Original/duplicate XXXXXXXXX

Tag number XXXXXXXXXXXXXXXXXXXX Batch ticket number X Batch revision X Previous revision X

Batch status XXXXXXXXXX Product name XXXXXXXXXXXXXXXXXXXX Program name XXXXXXXXXXXXXXXXXXXX

Batch base temp X.XXX Deg.C Batch base press X.XXX bar abs Batch equilib press X.XXX bar abs

Batch open/close parametersBatch start time XX/XX/XX XX:XX:XX Batch end date/time XX/XX/XX XX:XX:XX Start meter temp X.XXX Deg.C Batch end meter temp X.XXX Deg.C Start meter press X.XXX bar abs Batch end meter pres X.XXX bar abs Start meter dens X.XXX g/cc Batch end meter dens X.XXX g/cc

Batch open/close Cumulative TotalsStart IV total X.XXX m3 Close IV total X.XXX m3 Start GV total X.XXX m3 Close GV total X.XXX m3 Start ISV total X.XXX std m3 Close ISV total X.XXX std m3 Start GSV total X.XXX std m3 Close GSV total X.XXX std m3 Start mass total X.XXX kg Close mass total X.XXX kg

Batch TotalsInd vol total X.XXX m3 Gross vol total X.XXX m3 Ind std vol total X.XXX std m3 Gross std vol total X.XXX std m3 Mass total X.XXX kg Alarm total X.XXX Flowmeter errors X.XXX

Quantity Batch DetailsBatch program ID XXXXXXXXXX Batch request qty X.XXX Modified batch qty X.XXX

Weighted AveragesBatch av temp X.XXX Deg.C Batch av press X.XXX bar abs Batch av meter dens X.XXX kg/m3 Batch av base dens X.XXX kg/m3 Batch av degrees API X.XXX Batch av kine visc X.XXX cSt Batch av MF X.XXX Batch av K factor X.XXX pulse/m3 Batch av CTL X.XXX Batch av CPL X.XXX Batch av CCF X.XXX Batch av base BS&W X.XXX % Batch av BS&W X.XXX % Batch av CSW X.XXX Batch av oil bdens X.XXX kg/m3 Batch av oil deg API X.XXX Batch av water bdens X.XXX kg/m3

Alarm CountsAlarms during batch X If alarm count is not zero, refer to alarm history log to obtain alarm details.


7951 2510 (Ch18/AD) Page 18.17

18.2 Retrospective Batch Total Calculations The 7951 Flow Computer can re-calculate batch totals by applying updated values of key parameters. It then transmits a report through an appropriately configured serial port.

It is advisable to concentrate on the configuration and operation of standard batching (Section 18.1) and archiving (Chapter 9) before using any of the retrospective calculations.

18.2.1 OVERVIEW

Retrospective calculations can use new user-supplied values of key parameters to re-calculate the batch totals and update data of any archived batch record. An archived batch record is located, updated with new batch totals and re-archived. A revision number is included in the batch record for distinguishing it from the original batch record. This type of update is activated by selecting a “Yes” command. (See Section 18.2.2 on page 18.18)

Alternatively, retrospective calculations can be performed whilst a batch is in progress. In this case, the update can be activated by answering the acceptance prompt following a successful proving session. Batch totals in the current batch (transaction) record are then updated using a new ‘K factor’ or ‘Meter factor’ from the session. No other update parameters are considered. On completion of the batch, the current batch record is archived, as the original, in the normal way. (See Section 18.2.3 on page 18.20)

Table 18.6 has a full list of update parameters for supplying new values. Not all update parameters can be applied together. For example, where both the ‘K’ factor and ‘Meter factor’ update parameters have both been edited, the retrospective calculations apply only the most recently edited update parameter. Update parameters are applied in a fixed order as shown in Table 18.7.

The “Quantity Transaction Record” printed report is an output of the revised batch record. It does notexplicitly indicate differences between the original batch record and the revised batch record. Samples can be seen in Section Error! Reference source not found., starting on page 18.Error! Bookmark not defined..

Automatic printing of the batch report can be deactivated by navigating to the parameter <”Batch auto print”>, and then selecting the “Off” option.

Table 18.6: Update Parameters of Retrospective Calculation

UPDATE PARAMETER DIRECT IMPACT OF UPDATE CONDITION OF USE FOR UPDATE

Meter factor Gross Volume flow rate Newer value than the ‘K Factor’ update value K factor Indicated Volume flow rate Newer value than the ‘MF’ update value

%Water (std vol) * Net ‘Oil’/’Water’ calculations Net ‘Oil’/’Water’ calculations must be enabled Base density * Degrees API Newer value than API update value Degrees API * Base density Newer value than Base density update value

* Not used when performing retrospective calculations whilst a batch is in progress

Table 18.7: Priorities for Applying Update Parameters

ORDER OF APPLICATION UPDATE PARAMETER

1st. <“Meter factor”> or <“K factor”> * 2nd. <”BSW base”> 3rd. <”Base density”> or <”Degrees API”> *

* See Table 18.6 for explanation of parameter choice


Page 18.18 7951 2510 (Ch18/AD)

18.2.2 USING RETROSPECTIVE CALCULATIONS (ON ARCHIVED BATCH RECORDS)

This sub-section is an instructional guide to using retrospective calculations on any archived batch (transaction) record. Instructions assume that a batch has already been completed and archived. It is useful if a serial port is configured for and then connected to an ASCII compatible printer or PC running terminal software.

Activation Instructions: 1. Navigate to this parameter: <”Password”>/<”Enter password”>, and then enter the password for the

“Engineer” security level. (See Chapter 11 for reference pages on security levels and passwords)

2. Navigate to this menu: <”Batching”>/<”Retro calculations”>/<”Select batch”>

3. Select an archived batch (transaction) record:

(a) Nominate a primary search-key type….………….……{Parameter: <”Selection type”>}

This is for the auto-location of an archived batch record. Options are either searching the batch archive by ticket number or by archive record number

(b) Edit a value for the primary search-key…...…………...{Parameter: <”Batch ID”>}

Identify a sub-set of archived batch records by entering either an existing ticket number or an archived record number, as appropriate for the nominated primary search-key type

(c) Edit a value for the secondary search-key………...…..{Parameter: <”Batch revision”>}

Reduce the sub-set to a single archived batch record by editing a revision number that is a match for one of the archived batch records. Use zero if requiring the original (unmodified) batch record

Searches are automatically performed after editing the revision number and after editing the ticket/batch record reference number. Failed searches result in an INFO SYSTEM alarm being raised, which can be accepted and cleared from the Historical Alarm Log at any time.

4 Verify that the archived batch (transaction) record to be updated has been located At present, it is necessary to look in the Batch (Transaction) Archive menu system area…

(a) Press the PRINT MENU button

(b) Navigate to this menu: <”Archives”>/<”View / print logs”>/<”Transaction log”>/<”View snapshot”>

(c) Browse through the displayed data to see if it is the correct batch record

(d) Return to Step 2 if the batch record has not been located.

5 Program values into the update parameters

(a) Press the MAIN MENU button

(b) Navigate to this menu: <”Batching”>/<”Retro calculations”>/<”Retro values”>

(c) Work through the list of update parameters in Table 18.8.

Ignore the update parameters that are not relevant to your configuration or are of no interest.

Table 18.8: Check-list for Batch Update Parameters

UPDATE PARAMETER PARAMETER (AS DISPLAYED)

‘Meter factor’ or ‘K factor’ <”Meter factor”> or <”K factor”> % Water (by Std. Volume) <”BSW base”>

Base density or API <”Base density”> or <”Degrees API”>

Note: Some localised menu searching is required

Note: Retrospective calculations are not performed unless a minimum of one update parameter has been edited since Step 2. Initial values for the update parameters are automatically copied from the auto-located archived batch record.


7951 2510 (Ch18/AD) Page 18.19

(Instructions continued…)

6. Select the scope of the retrospective calculation

(a) Locate the menu data page with “Retro calc type” as the descriptor

(b) Select the option with either “All of batch” or “Part of batch”

(c) When the “part of batch” option is selected, navigate to the menu data page with “Retro calc qty type”. Edit a quantity to establish the scope of all updates.

7. Activate the retrospective calculation

(a) Locate the parameter with “Recalculate” as the descriptor.

(b) Select the option with “Yes”.

Calculations are performed quickly and are normally completed within one machine cycle. The batch (transaction) record is updated with revised values and then re-archived with the same ticket/archive record reference number and a new revision number.

8. View the modified batch transaction record

Options:

(a) View from Batch (Transaction) Archive menu system area

Press the PRINT MENU button Navigate to: <”Archives”>/<”View / print logs”>/<”Transaction log”>/<”View snapshot”> Browse through the displayed data to see if it is the correct batch record

(b) View from printed report

(End of Activation Instructions)


Page 18.20 7951 2510 (Ch18/AD)

18.2.3 USING RETROSPECTIVE CALCULATIONS (ON THE CURRENT BATCH RECORD)

This is a guide to activating retrospective calculations on near completion of a successful proving session, whilst a batch is still in progress.

Activation Instructions: The following instructions assume that a successful prove-session has occurred, and a new factor has just been accepted for use in subsequent fiscal flow calculations.

1. Figure 18.9 shows the screen prompt that follows acceptance of a new ‘K factor’ or ‘Meter factor’. This is the opportunity to perform retrospective calculations with the newly accepted flow factor.

(a) Press a lettered-button that is alongside the option you require. Use Table 18.9 to decide which option to select.

Figure 18.9: "Apply to Batch?" Screen

Table 18.9: "Apply to Batch?" Options

Option Purpose of Option

No Do not perform retrospective calculations - continue with Step 3Part Re-calculate recent part of flow for all current batch total retrospectively - continue with Step 2All Re-calculate all product flow for each current batch total retrospectively - continue with Step 3

2. Figure 18.10 shows the prompt that appears after selecting the “Part” (‘c’ button) option from Step One.Specify the ‘part of batch’ as a quantity in the units of measurement displayed. This will be a value in either volumetric or mass units, depending on the configuration for quantity-type batch operations.

(a) Press the ‘c’ button to start the editing process (b) Edit a value using the numeric keypad (c) Press the ‘c’ button to confirm the edited value.

Figure 18.10: "Enter batch quantity to adjust" screen

3. Continue with the prompts until the menu system re-appears. Retrospective calculations then take place (if activated by Step 1) instantly and are completed within one machine cycle, therefore having a negligible effect on the live batch transaction recording.

Chapter 19 Flow Computer Basic Language

7951 (Ch19/AA) Page 19.1

19. Flow Computer Basic Language (FC-BASIC) This chapter explores the support for creating additional 7951 flow computer features using the built-in programming language called FC-BASIC.

19.1 Introduction

19.1.1 What is FC-Basic?

FC-BASIC is the 7951 flow computer version of the traditional computer programming language known as BASIC (Basic All-purpose Symbolic Instruction Code). Although not grabbing headlines in recent years, those who owned microcomputers in the 1980’s will still fondly remember BASIC.

Functional Overview Lines of FC-BASIC language are typically edited on a PC (or similar system) to form a program script. If using a PC running Windows, you may wish to use the Notepad program as the editor. Once you have finished editing, save the program script as a text file.

The next step is to transfer the program script (text file), to the flow computer through an RS-232 serial cable, interconnecting PC serial port and 7951 serial port. If using a PC running Windows, you may wish to use Terminal (Windows 3.1) or Hyperterm for carrying out the transfer. No more than one program script can be stored in the 7951. The length of script is limited by memory availability.

You may also use the same PC application to enter FC-BASIC commands directly: LIST, DELETE and VERIFY. For information on these commands, turn to page 19.3.

Once transferred to the flow computer, the FC-BASIC script can be run. Assuming there are no errors, it executes repeatedly once every machine cycle.

19.1.2 What can FC-BASIC be used for?

Typical uses of FC-BASIC are:

Live input to software parameters (see below).

The generation of text-based logs at pre-determined times, weekly, monthly, or intervals of days.

Automatic triggering of a prove-session after a pre-determined period, after a pre-set volume of flow, or if the fluid viscosity has changed.

Automatic opening or closing of metering-runs (streams) depending on station flow rate.

Grab sampler handling. An alarm can be raised when the sample is 90% full.

Changing engineering units.

Algorithms.

Reports.

Totalisation over periods of time not supported by the interval log.

Control of external devices via a digital or analog output.

Monitoring of external devices via a digital or analog input.

Note: Before running the FC-BASIC script, you will need to be at PROGRAMMER security level.

Note: It is assumed that the readership has a working knowledge of a Windows-based PC, is reasonably familiar with interconnecting the PC and Flow Computer and has some experience with computer programming.


Page 19.2 7951 (Ch19/AA)

Listed below are the calculations that can source a result from a FC-BASIC program (see Chapter 11). That associated parameter (location) can be made “Live”, and the result from the FC-BASIC program can be put into the live location without the possibility of another part of the 7951 overwriting the value. Any floating-point parameter can be written into by a FC-BASIC program.

Base Density B.

Density B. Dynamic viscosity. Energy. Isentropic.

Line pressure. SG B.

19.1.3 What needs to be configured on the 7951?

Apart from basic 7951 communication parameters, there are a few FC-BASIC simple set-up parameters:

FC-BASIC

1. Ensure you at PROGRAMMER security level.

2. Navigate to this menu: <”Configure”>/<”FC Basic”> to find these parameters:

<Enable/disable> A menu ‘soft-command’ to toggle between enabling program scripts to run and preventing program scripts from running.

<Cycle timeout> This defines the maximum period a program is allowed to execute before it is suspended and a new machine cycle is begun. At the end of the next machine cycle the program is allowed to execute from the line at which it was suspended.

<Program timeout> This defines the maximum period a program is allowed to execute before it is terminated and a timeout alarm is generated. At the end of the next machine cycle program execution begins again from line one.

<End-of-line in> Toggle between “Carriage-return” or “Line-feed” to determine how FC-BASIC distinguishes the end of a line in a program script. (Whenever using Hyperterm, as the ‘text file’ transfer application, it is best to select ‘line-feed’ options on both PC and 7951.)

<End-of-line out> Toggle between “Carriage-return” or “Line-feed” or “<cr><lf>” to determine the end-of-line character sequence FCBasic will use when printing.

SERIAL PORTS

1. One 7951 serial port connection will be required for issuing direct commands (e.g. LIST) and the transfer of FC-BASIC program script (text file) from an external system (e.g. PC, MAC, etc.) to the 7951. Basic communication parameters are as guided in Chapter 7, for RS-232 set-up. The exception is <Function>, which must be “FC Basic”.

2. To view the output of a FCBasic program print statement, it is necessary to set-up a serial port as “Printer”. Any ASCII compatible device, such as a printer or a PC acting as a terminal (See Chapter 7.) can be attached to the serial port. If a program contains a print statement then a port must be configured before the FCBasic program is verified.


7951 (Ch19/AA) Page 19.3

19.2 EDITOR COMMANDS The following commands can be issued to the serial port configured for FC-BASIC.

LIST Lists all lines of the FC-BASIC script currently stored in the 7951.

DELETE Deletes the entire FC-BASIC script currently stored in the 7951.

VERIFY The FC will execute a program only after this command has been entered. The FC will check the program for errors. If there are no errors then <Health check><FC Basic><Status> will show “Success” and the program will be executed at the end of the next machine cycle. Otherwise an error message will be generated at the serial port configured for FCBasic, and FCBasic status will show “Program not ready”.

19.3 COMMAND DIRECTORY This section provides information on the use of FC-BASIC commands. All FC-BASIC statement lines are preceded by a line number, which identifies the position within the program script. Line numbers can range from 1 to 9999 inclusive.

19.3.1 STATEMENTS

REM (REMark)

Purpose: It allows a script to be documented. All characters on the line, beyond the REM command, have no effect on the FC-BASIC program.

Example: 10 REM *** This is a REMark statement ***

IF, THEN, [ELSE] ENDIF Purpose: IF is always followed by a Boolean expression. When the expression evaluates to TRUE,

the program script execution continues with the next statement line following the THEN.Otherwise, the expression evaluates to FALSE and program script execution continues with the next statement line following the ELSE or the ENDIF where there is no ELSE.

Example1: 10 B = 1 20 IF B <> 2 THEN B = B + 1

Example2: 10 A = 1 20 IF A <> 2 THEN 30 A = A + 1 40 ELSE 50 A = A + 2 60 ENDIF

GOTO (GO TO)

Purpose: Transfers ‘interpret and execute’ control directly to another line in the same program script.

Example: 10 GOTO 50 20 REM *** LINE 20 IS NEVER REACHED *** : 50 REM *** JUMPED HERE FROM LINE 10 ***


Page 19.4 7951 (Ch19/AA)

GOSUB, RETURN Purpose: GOSUB temporarily transfers program control directly to another line in the same program

script. When the RETURN is encountered, program control reverts back to the next statement line following the original GOSUB.

Note: This FC-BASIC statement can be nested, and recursive, limited only by memory availability.

Example: 10 GOSUB 50 20 REM *** LINE 20 IS REACHED *** : 50 REM *** TEMPORARY JUMP HERE FROM LINE 10 *** 60 A = A + 1 70 B = B + 1 80 RETURN 90 REM *** NEVER REACH LINE 90 SINCE CONTROL ALWAYS 100 REM *** RETURNS TO LINE 20

FOR X = Y TO Z, NEXT [STEP W] Purpose: Executes a loop of statement(s) a number of times. The loop always executes at least one.

The variable X, an integer value, is initialised with the value of Y, which can be a constant or a variable. W is optional and may be positive or negative. If missing, the value 1 is assumed.

When the NEXT is reached, W is added to X. The X is compared to Y. If W is positive, the loop will execute again as long as Z is greater than X. Conversely, when W is negative, the loop will execute again as long as Z is less than X.

The loop stops when X is equal to or greater than Z. On exiting the loop, X contains the value last used for the comparison.

Example: 10 B = 0 20 FOR A = 1 TO 10 30 B = B + A 40 NEXT

WHILE, WEND Purpose: Executes a loop of statement(s) until a Boolean expression evaluates to FALSE. The loop

does not execute unless the Boolean expression initially evaluates to TRUE.

The WHILE is always followed by a Boolean expression. Statement lines between WHILEand WEND will be executed as long as the expression evaluates to TRUE. When the expression evaluates to false, ‘interpret and execute’ control continues with the next statement line following WEND.

Example: 10 A = 1 10 WHILE A < 10 20 A = A +1 30 WEND


7951 (Ch19/AA) Page 19.5

STOPPurpose: Stops the program script execution at this line.

Example: 10 STOP

TIMEPurpose: Obtains the seconds value from an internal clock timer. The value can be used in

calculations within the program script. It is useful for tracking the elapsed time between loops. TIME will return a 6 element array containing 0=seconds, 1=minutes, 2=hours, 3=day, 4= month and 5=year.

See also: TIMER and ONTIMER

TIMER(1...8)Purpose: There are up to 8 countdown timers available. They can be assigned a period of seconds in

the range of 0 to (232 –1)/1000. The timers run backwards, decreasing by each cycle. On reaching zero, ONTIMER GOSUB is invoked.

To cancel a timer, set the period to 0 (zero seconds).

ONTIMER(1...8), GOSUB Purpose: When a particular timer reaches 0 (zero seconds), program control is transferred directly to

another line in the script. As with all GOSUB statements, there must be a RETURN.

Note: It is only ever invoked when the particular timer reaches 0, irrespective of where it is positioned in the script.

See also: TIMER

Example: 100 if InitFlag = FALSE then 110 ontimer(1) gosub 200 120 timer(1) = 10 130 LOC_SP_EQU1_A = 1523 ! Location number for applic 1540 140 InitFlag = TRUE 150 endif 160 199 stop

200 REM *** JUMPS HERE ONLY WHEN TIMER(1) REACHES ZERO *** 210 A = A + 1 220 poke(LOC_SP_EQU1_A, A) 230 timer(1) = 10 ! reinitialise timer 240 return


Page 19.6 7951 (Ch19/AA)

DIM (DIMensional array)

Purpose: Declares a variable as a one-dimensional (flat) array of a specified size. A variable array can store values of floating-point numbers or integers in particular positions (spaces).

Note: Array declarations do not directly affect program control or the way a script is executed.

Example: 10 DIM turbine_array(2) as float : 40 REM Set-up turbine array with values in positions 0, 1 and 2 50 turbine_array(0) = 0.5 60 turbine_array(1) = 5.0 70 turbine_array(2) = 2.2

PRINTPurpose: A means to output simply formatted data through a serial port that has been configured for

connection to an ASCII compatible device, such as a printer.

Two special formatting functions, SPC and TAB, as provide for use in PRINT statements.

SPC(n) is used to insert space characters in the output, where n is the number of spaces required.

TAB(N) is used to position the insertion point to an absolute column number, where n is the column number. Use TAB with no argument to position the insertion point at the beginning of the next print zone.

Note: If a ‘;’ is used as a separator, the next print item is output in the next print zone.

Examples: 10 PRINT “THIS IS A PRINT STATEMENT” :

40 FOR A = 1 TO 5 50 PRINT “A = ”;A 60 NEXT

19.3.2 BOOLEAN EXPRESSIONS

FALSE = 0 A value of ZERO is equal to logical FALSE TRUE<>FALSE True is any value that is not equivalent to FALSE

19.3.3 LOGICAL AND BITWISE OPERATORS

NOTANDORXOR


7951 (Ch19/AA) Page 19.7

19.3.4 RELATIONAL OPERATORS

<>><<=>=

19.3.5 ARITHMETIC OPERATORS

+-*/^MODDIV

19.3.6 ARITHMETIC FUNCTIONS

ABSACOSASINATANBSGNCOSEXPINTLNPOWSINSQRTTANTIMEPEEKPOKEGETSTATUSSETSTATUS

19.3.7 PRE-DEFINED ARRAYS

LOC(XXX) 7951 database variable access.

AIN(X) Analogue input access

AOUT(X) Analogue output access

DIN(X) Digital (status) input access

DOUT(X) Digital (status) output access

VIN (X) Valve status access

VOUT(X) Valve command access

TIMER(X) See TIMER entry in earlier section


Page 19.8 7951 (Ch19/AA)

19.3.8 PRE-DEFINED CONSTANTS

TRUE -1 (NOT 0 is –1)

FALSE 0

LIVE 0

SET 1

FAIL 2

FB 3

19.3.9 VARIABLE TYPES

Float 64-bit floating point number

Integer Signed 32-bit number

Array Each element a float

19.3.10 DIRECT 7951 DATABASE ACCESS

PEEK(X) Read last data of location X

POKE(X) Write data to location X

GETSTATUS(X) Read status of location X. Returns a numeric value, equal to one of the pre-defined constants: LIVE, SET, FAIL or FB

SETSTATUS(X, N) Write status of location X. The N is a numeric value, equal to one of the pre-defined constants: LIVE, SET, FAIL or FB


7951 (Ch19/AA) Page 19.9

19.4 SAMPLE FC-BASIC SCRIPTS This section provides a few samples that can be adapted to suit other applications.

19.4.1 FC-BASIC Sample Script: AGA5 Algorithm

Delete1000 rem **** PROGRAM AGA5 **** 1010 rem 1020 rem This function calculates calorific value using the AGA5 1030 rem equation:- 1040 rem 1050 rem 0.001970 - Mx 1060 rem Cm = 0.02035 + ------------- 1070 rem SG 1080 rem 1090 rem where: Mx = (C02 * 0.0329) + (N2 * 0.0217) 1100 rem 1110 rem Result is in MJ/kg. A conversion factor is applied to convert 1120 rem the units of the AGA5 equation (dekatherms/lb) to MJ/kg. 11301140 if InitFlag = 0 then gosub 2000 ! Initialise 11501160 rem Get Data From Database 1170 rem ---------------------- 1180 SG = peek(LOC_SG_PRIME_VALUE) 1190 CO2 = peek(LOC_LIVE_CO2_VALUE) ! per unit (i.e. Percent/100) 1200 N2 = peek(LOC_LIVE_N2_VALUE) ! per unit (i.e. Percent/100) 12101220 rem Perform Calculation 1230 rem ------------------- 1240 Mx = (CO2 * 0.0329) + (N2 * 0.0217) 1250 if SG <> 0 then 1260 Cm = 0.02035 + ((0.001970 - Mx) / SG) 1270 else 1280 Cm = 0 1290 endif 1300 CmMJKG = Cm * DEKATHERMS_PER_LB_TO_MJ_PER_KG 13101320 rem Store Result In Database 1330 rem ------------------------ 1340 LocStatus = getstatus(LOC_ENERGY_VALUE) 1350 if LocStatus = LIVE then 1360 poke(LOC_ENERGY_VALUE, CmMJKG) 1370 endif 1380 stop 2000 rem **** Subroutine Initialise **** 20102020 rem Calculation Constants 2030 DEKATHERMS_PER_LB_TO_MJ_PER_KG = 2325.2159 20402050 rem Database Constants 2060 DBM_OPT_ENERGY_FCBASIC = 5 20702080 rem Location Numbers For Gas Application 1510 2090 LOC_ENERGY_VALUE = 39


Page 19.10 7951 (Ch19/AA)

2100 LOC_OPT_ENERGY_CALC_SEL = 41 2110 LOC_LIVE_CO2_VALUE = 901 2120 LOC_LIVE_N2_VALUE = 909 2130 LOC_SG_PRIME_VALUE = 718 21402150 rem Select Energy Calc From FCBasic (must use loc for option locations) 2160 loc(LOC_OPT_ENERGY_CALC_SEL) = DBM_OPT_ENERGY_FCBASIC 21702180 rem Sensible initial values (must use loc for live/set locations) 2190 loc(LOC_LIVE_CO2_VALUE) = 0.00201 2200 loc(LOC_LIVE_N2_VALUE) = 0.00139 22102220 InitFlag = 1 2999 return Verify


7951 (Ch19/AA) Page 19.11

19.4.2 FC-BASIC Sample Script: Monthly Batch Report

Delete1000 rem **************** PROGRAM - MONTHLY BATCH REPORT **************** 1010 rem 1020 rem This program calculates monthly totals and maximum and minimum 1030 rem values of process quantities. The calculated totals and max/min 1040 rem quantities are listed below. 1050 rem 1060 rem Totals 1070 rem ------1080 rem BaseVol month total 1090 rem Energy month total 1100 rem1110 rem Process Quantities 1120 rem ------------------ 1130 rem Meter run temperature 1140 rem Meter run pressure 1150 rem Meter run DP 1160 rem Meter run prime density 1170 rem Densitometer temperature 1180 rem 1190 rem Note: The Basic interpreter initialises all program variables 1200 rem to zero before the program executes for the first time. 12101220 dim Max(5) as float, Min(5) as float, Samples(5) as integer 1230 dim LocIds(5) as integer 12401250 if InitFlag = 0 then gosub 2000 ! Initialise 12601270 gosub 3000 ! Update max/min values 1280 gosub 4000 ! Update_Totals 12901300 Month = time(4) 1310 if Month <> LastMonth then 1320 gosub 5000 ! Print_Report 1330 LastMonth = Month 1340 endif 13501900 stop 2000 rem **** Subroutine Initialise **** 20102020 rem Program Constants 2030 rem ----------------- 2040 NUMBER_OF_MAXMIN = 5 2050 LINE_TEMP_INDEX = 1 2060 DENS_TEMPA_INDEX = 2 2070 LINE_PRESS_INDEX = 3 2080 DIFF_PRESS_INDEX = 4 2090 LINE_DENS_INDEX = 5 21002110 rem Location Numbers For Gas App 1510 2120 rem --------------------------------- 2130 LOC_BASE_VOL_TOTAL = 87 2140 LOC_BASE_VOL_TOTAL_ROLLOVER = 88 2150 LOC_ENERGY_TOTAL = 92


Page 19.12 7951 (Ch19/AA)

2160 LOC_ENERGY_TOTAL_ROLLOVER = 93 21702180 LOC_LINE_TEMP_VALUE = 416 2190 LOC_DENS_TEMPA_VALUE = 438 2200 LOC_LINE_PRESS_VALUE = 321 2210 LOC_DIFF_PRESS_VALUE = 339 2220 LOC_LINE_DEN_PRIME_VALUE = 677 22302240 rem FC Basic Location Numbers For Gas App 1510 2250 rem ------------------------------------------ 2260 LOC_FCBASIC_REAL_1 = 2407 2270 LOC_FCBASIC_REAL_2 = 2408 2280 LOC_FCBASIC_REAL_3 = 24092290 LOC_FCBASIC_REAL_4 = 2410 2300 LOC_FCBASIC_REAL_5 = 2411 2310 LOC_FCBASIC_REAL_6 = 2412 2320 LOC_FCBASIC_REAL_7 = 2413 2330 LOC_FCBASIC_REAL_8 = 2414 2340 LOC_FCBASIC_REAL_9 = 2415 2350 LOC_FCBASIC_REAL_10 = 2416 2360 LOC_FCBASIC_REAL_11 = 2417 2370 LOC_FCBASIC_REAL_12 = 2418 23802390 rem Simulated Locations 2400 rem ------------------- 2410 LOC_BASE_VOL_MONTH_TOTAL = LOC_FCBASIC_REAL_1 2420 LOC_ENERGY_MONTH_TOTAL = LOC_FCBASIC_REAL_2 24302440 LOC_BASE_VOL_LAST_MONTH_TOTAL = LOC_FCBASIC_REAL_3 2450 LOC_ENERGY_LAST_MONTH_TOTAL = LOC_FCBASIC_REAL_4 24602470 rem Initialise Non-Zero Program Variables 2480 rem ------------------------------------- 2490 BaseVolMonthTotal = peek(LOC_BASE_VOL_MONTH_TOTAL) 2500 EnergyMonthTotal = peek(LOC_ENERGY_MONTH_TOTAL) 2510 LastMonth = time(4) 25202530 rem Initialise Arrays 2540 rem ----------------- 2550 LocIds(1) = LOC_LINE_TEMP_VALUE 2560 LocIds(2) = LOC_DENS_TEMPA_VALUE 2570 LocIds(3) = LOC_LINE_PRESS_VALUE 2580 LocIds(4) = LOC_DIFF_PRESS_VALUE 2590 LocIds(5) = LOC_LINE_DEN_PRIME_VALUE 26002610 for i = 1 to NUMBER_OF_MAXMIN 2620 Max(i) = 0 2630 Min(i) = 0 2640 Samples(i) = 0 2650 next i 26602670 InitFlag = 1 26802690 return


7951 (Ch19/AA) Page 19.13

3000 rem **** Subroutine Update_MaxMin **** 30103020 for i = 1 to NUMBER_OF_MAXMIN 3030 LocId = LocIds(i) 3040 Value = peek(LocId) 3050 if( Value > Max(i) or Samples(i) = 0 ) then 3060 Max(i) = Value 3070 elseif( Value < Min(i) or Samples(i) = 0 ) then 3090 Min(i) = Value 3100 endif 3110 next i 31203130 return 4000 rem **** Subroutine Update_Totals **** 40104020 rem Get Data From Database 4030 rem ---------------------- 4040 BaseVolTotal = peek(LOC_BASE_VOL_TOTAL) 4050 EnergyTotal = peek(LOC_ENERGY_TOTAL) 40604070 rem Calculate BaseVolMonthTotal 4080 rem --------------------------- 4090 Inc = BaseVolTotal - LastBaseVolTotal 4100 if Inc < 0 then 4110 Rollover = peek(LOC_BASE_VOL_TOTAL_ROLLOVER) 4120 Inc = Inc + Rollover 4130 endif 41404150 BaseVolMonthTotal = BaseVolMonthTotal + Inc 41604170 rem Calculate EnergyMonthTotal 4180 rem -------------------------- 4190 Inc = EnergyTotal - LastEnergyTotal 4200 if Inc < 0 then 4210 Rollover = peek(LOC_ENERGY_TOTAL_ROLLOVER) 4220 Inc = Inc + Rollover 4230 endif 42404250 EnergyMonthTotal = EnergyMonthTotal + Inc 42604270 rem Store Totals In Database 4280 rem ------------------------ 4290 poke(LOC_BASE_VOL_MONTH_TOTAL, BaseVolMonthTotal) 4300 poke(LOC_ENERGY_MONTH_TOTAL, EnergyMonthTotal) 43104320 rem Update Values For Next Calculation 4330 rem ---------------------------------- 4340 LastBaseVolTotal = BaseVolTotal 4350 LastEnergyTotal = EnergyTotal 43604370 return 5000 rem **** Subroutine Print_Report **** 50105020 BaseVolMonthTotal = peek(LOC_BASE_VOL_MONTH_TOTAL) ! std m3 5030 EnergyMonthTotal = peek(LOC_ENERGY_MONTH_TOTAL) ! MJ


Page 19.14 7951 (Ch19/AA)

50405050 print " " 5060 print " MONTHLY REPORT" 5070 print " ==============" 5080 gosub 6000 ! print date/time 5090 print " " 5100 print "Month Total" 5110 print "-----------" 5120 print "Base vol total "; BaseVolMonthTotal, "std m3" 5130 print "Energy total "; EnergyMonthTotal, "MJ" 5140 print " " 5150 print "Maxima" 5160 print "------" 5170 print "Meter temperature "; Max(LINE_TEMP_INDEX) 5180 print "Density1 temperature "; Max(DENS_TEMPA_INDEX) 5190 print "Meter pressure "; Max(LINE_PRESS_INDEX) 5200 print "Diff pressure "; Max(DIFF_PRESS_INDEX) 5210 print "Prime density "; Max(LINE_DENS_INDEX) 5220 print " " 5230 print "Minima" 5240 print "------" 5250 print "Meter temperature "; Min(LINE_TEMP_INDEX) 5260 print "Density1 temperature "; Min(DENS_TEMPA_INDEX) 5270 print "Meter pressure "; Min(LINE_PRESS_INDEX) 5280 print "Diff pressure "; Min(DIFF_PRESS_INDEX) 5290 print "Prime density "; Min(LINE_DENS_INDEX) 5300 print " " 5310 print "************* END OF REPORT ******************" 53205330 BaseVolMonthTotal = 0 5340 EnergyMonthTotal = 0 5350 poke(LOC_BASE_VOL_MONTH_TOTAL, BaseVolMonthTotal) 5360 poke(LOC_ENERGY_MONTH_TOTAL, EnergyMonthTotal) 53705380 for i = 1 to NUMBER_OF_MAXMIN 5390 Max(i) = 0 5400 Min(i) = 0 5410 Samples(i) = 0 5420 next i 54305440 return 6000 rem **** Subroutine Print_DateAndTime **** 60106020 day = time(3) 6030 month = time(4) 6040 year = time(5) 60506060 hours = time(2) 6070 mins = time(1) 6080 secs = time(0) 60906100 print day; "/"; month; "/"; year, hours; ":"; mins; ":"; secs 61106120 return Verify

Appendix A Glossary

7951 (Appx-A/AF) Page A.1

Appendix A Glossary

AADC See Analogue to digital converter

Address A number which uniquely identifies a location.

Alarm An indicator which shows when a failure has occurred. Alarms are classified as System, Input or Limit.

API American Petroleum Institute

Analogue input An input where information is received in analogue form.

Analogue output An output from which information is transmitted in analogue form.

Analogue to digital converter A circuit that converts analogue voltages or currents into digital (usually binary) numbers which can then be processed by computers. The digital signal gives the amplitude of the analogue signal at a particular instant. See also Digital to analogue converter.

AUI Short for Attachment Unit Interface, the portion of the Ethernet standard that specifies how a cable is to be connected to a transceiver that plugs into a 15-pin socket

BBar A unit of pressure. 1 bar = 105 Nm2.

Base condition Base or Standard Conditions give the volume which would have been transferred if the temperature were at a pre-defined figure. The actual values for base temperature and pressure vary from country to country.

Base density Density of a fluid measured under base conditions.

British Thermal Unit The energy required to raise the temperature of one pound of water through one degree Fahrenheit.

BTU See British Thermal Unit.

CCalibrate To assess the performance of an item of equipment against that of

another one whose accuracy is known.

Appendix A Glossary

Page A.2 7951 (Appx-A/AF)

Calibration certificate Each transducer is calibrated before it leaves the factory. The details (together with the transducer’s serial number) are recorded on a Calibration Certificate.

Calibration constant Among the information given on the calibration certificate are some constants (unique to that transducer) which compare the transducer’s actual performance against a standard. The signal converter must know these constants before it can calculate accurate results.

The constants are designated: K0, K1, K2, and so on.

Calorific value The energy content of a substance (usually a gas).

Chassis earth In a large installation where the chassis and instrumentation are earthed separately, this is the “dirty” earth to which instrument chassis are connected.

Checksum In data transmission, a checksum is a number which is added to a string of data and whose value is related to that data. It is used to check that the data has been transmitted accurately.

Connector The part of a cable that plugs into a port or interface to connect one device to another. Most connectors are either male (containing one or more exposed pins) or female (containing holes in which the male connector can be inserted).

Configuration 1. The setting up of an instrument (by entering data, setting fallback values, setting alarms, and so on) so that it works according to your requirements.

2. The method by which transducers and other inputs and outputs are physically connected to the 7951

Conventional pipe prover This has a volume between detectors that permits a minimum accumulation of 10,000 direct (unaltered) pulses from the meter under test.

Covimat A rotational viscometer.

Crystal factor A multiplying factor which accounts for the difference between the actual frequency of a particular crystal and its theoretical frequency.

CV See Calorific value

DDAC See Digital to analogue converter

Damping Suppressing the oscillations in a vibrating body or medium.

Degree API Used in the petroleum industry to describe the density of petroleum products. A degree API is given by:

141.5/(SG at 60oF) - 131.5

Values lie within the range -1 to +101, the larger the number the lighter the oil.

Appendix A Glossary


Degree Baume A unit on an arbitrary scale which can be converted into actual SG values. Used when describing the sugar content of aqueous solutions.

Degree Brix A unit on an arbitrary scale which can be converted into actual SG values. Used when describing the sugar content of aqueous solutions.

Density The measured density of the fluid in a pipeline.

Differential pressure The difference in pressure at two points in a pipeline.

Digital to analogue converter A circuit that converts digital signals into analogue equivalents. See also Analogue to digital converter.

Download To send data or programs to another (usually subsidiary) instrument. (Opposite of Upload).

DP See Differential pressure

EEMC Electro-Magnetic Compatibility

Event A change in the system operation. Events may be caused by the user (such as setting a parameter or changing the security) or by alarms (if, for example, a fallback is invoked when the system fails).

External connection A generic term which covers: inputs, outputs, power supplies and serial communications; in short, anything connected to the 7951.

FFallback mode A description of the system when it is using a Fallback value.

Fallback value A value used as a temporary substitute for a parameter when a live input which is used to calculate the parameter fails.

Flow computer An instrument which monitors flow rates and densities of gases and liquids. It does this by communicating with transmitters such as pressure, temperature, level, flow, density and analytical instruments. These measurements are then corrected for temperature, pressure and velocity of sound.

FS Full scale.

Full composition The composition of a gas used in calculating energy and compressibility.

Appendix A Glossary


HHazardous area An area where there is a risk of fire or explosion.

Health check a check that all inputs and devices connected to the 7951 are operating normally.

Hg The chemical symbol for the element Mercury.

Historical log A log of every alarm received by the 7951.

Hub A common connection point for devices in a network. Hubs are commonly used to connect segments of a LAN. A hub contains multiple ports. When a packet arrives at one port, it is copied to the other ports so that all segments of the LAN can see all packets.

A passive hub serves simply as a conduit for the data, enabling it to go from one device (or segment) to another. So-called intelligent hubsinclude additional features that enables an administrator to monitor the traffic passing through the hub and to configure each port in the hub. Intelligent hubs are also called manageable hubs.

IInstrumentation earth In a large installation where the instrumentation and chassis are

earthed separately, this is the “clean” earth to which the instrumentation is connected.

Interrogate To ask another part of a system to supply information.

JJ See Joule.

Joule The unit of work. 1J = 1N/m2.

Jumper A metal bridge that closes an electrical circuit. Typically, a jumper consists of a plastic plug that fits over a pair of protruding pins. Jumpers are sometimes used to configure add-on (option) boards. By placing a jumper plug over a different set of pins, you can change a board's parameters.

KK-factor The K-factor relates the output from a flow meter to a specific set of

units. For volume output meters such as turbines, it is often quoted as pulses per meter cubed.

Kinematic viscosity The ratio of the dynamic viscosity of a fluid to its density.

Appendix A Glossary


LLED See Light-emitting diode.

Light-emitting diode A diode which light up when current flows through it. LED’s are usually used as indicator lights on instruments.

Limit Limits are upper and lower values between which a measured parameter is expected to be. If the parameter is outside these limits, it can trigger an alarm if you have set the system to do so.

Live A value is live if it can be altered automatically as a result of some internal calculation or transducer input. (See also: Set.)

Location An area of computer memory where data is stored. Information can be written to it from the keyboard, a remote computer, or automatically by the sensors.

Location ID A number which uniquely identifies a location.

MMass flow rate The rate at which a given mass of fluid flows through a transducer.

MAU Short for Media Access Unit, an Ethernet transceiver

MODBUS/TCP MODBUS/TCP is a variant of the MODBUS family of simple, vendor-neutral communication protocols intended for supervision and control of automation equipment. Specifically, it covers the use of MODBUS messaging in an ‘Intranet’ or ‘Internet’ environment using the TCP/IP protocols. The most common use of the protocols at this time are for Ethernet attachment of PLC’s, I/O modules, and ‘gateways’ to other simple field buses or I/O networks.

Mode The operational state of the instrument.

Monitor To keep a constant check on the status of a system or process.

Multiples of numbers TMm

teramega milli

1012

106

10-3

G k

giga kilo micro

109

103

10-6

Multiview A user-defined display which can show up to four lines of information of your choice. Typically, each line comprises text (such as a parameter name) and a value for the parameter.

PPa See Pascal.

Appendix A Glossary


Pascal The unit of force. 1 Pa = 1N/m2

Percent mass The percentage that the mass of a substance has compared to the total mass for a mixture of substances of which it is a part.

Periodic time The duration of one cycle of a wave-form, equal to the inverse of the frequency.

Platinum resistance thermometer A highly-accurate thermometer, based around a coil of very pure platinum wire, which is extremely stable over time. It can be used instead of an analogue input to the signal converter or flow computer.

POST See Power-on self test.

Power-on self test A standard routine which an item of equipment goes through when it is powered up to make sure that it is operating correctly. The progress of the test is usually shown on the instrument display.

Protect ground Another name for Chassis earth.

PRT See Platinum resistance thermometer.

Pressure The measured pressure of the fluid in the pipeline.

Primary variable A variable (such as time or distance) which is directly measured.

psi Pounds per square inch. Imperial units of pressure.

Pulse output An output of single pulses, sent to equipment such as pulse summators or electro-mechanical totalizers.

PV See Primary variable

RRadio frequency interference Interference from sources which transmit at radio frequencies; that is,

frequencies in the range of about 100kHz to about 300GHz.

Reynolds number A dimensionless constant given by vlvlRe

Where: = fluid viscosity l = length

= kinematic viscosity = density

RFI See Radio frequency interference

RS-232 An international standard for serial data transmission. It specifies voltage levels, timing and control.

Appendix A Glossary


S Saybolt viscosity A viscosity measured using methods developed by the Saybolt

company. It is obtained by timing how long the fluid takes to flow out of a cup through a hole of known size. The viscosity is expressed in units of time.

Security code A code or password which a user must key in before being allowed access to all or part of a system.

Sensor Another name for a transducer.

Set A value is SET if it is keyed in by the user and does not change unless the user changes it. (See also: Live.)

Set-up routine A procedure for setting up or configuring a system.

SG See Specific gravity

Signal converter A device which converts one signal into another. Its main use is in quality measurement systems such as brewing where the output is used by a control or monitoring system.

Specific gravity The mass per unit volume of a fluid.

Standard condition See Base condition

Status The condition of part of a system; for example, whether it is on, off, and so on.

Status display A display which summarises the contents of the Historical log and gives an indication of the current status of the system.

TTCP/IP Abbreviation for Transmission Control Protocol/Internet Protocol, the

suite of communications protocols used to connect hosts on the Internet. TCP/IP uses several protocols, the two main ones being TCP and IP. TCP/IP is built into the UNIX operating system and is used by the Internet, making it the de facto standard for transmitting data over networks. Even network operating systems that have their own protocols, such as Netware, also support TCP/IP.

Temperature The measured temperature of the fluid in the pipeline.

Temperature correction Transducers are typically designed to work at 20°C. A correction must be applied when working at other temperatures.

Text descriptor Text which you can enter into the signal converter. Typically, this is a parameter name when you configure Multiview.

Therm Unit of heat. 1 therm is the heat required to raise 1000 pounds of water through 100°F.

Appendix A Glossary


Transducer A device which converts a physical quantity (such as temperature or pressure) to a voltage or some other electrical quantity that can be measured and analysed.

U Upload To receive data or programs from another instrument. (Opposite of

Download).

VViscosity In a liquid, the resistance to that force which tends to make the liquid

flow.

Volume flow rate The rate at which a given volume of fluid flows through the system.

VOS Velocity of Sound

WWizard One of the “standard” configurations whch you can select instead of

configuring the 7951 from scratch. You can edit the resulting configuration to meet your requirements.

Wobbe index A measure of the amount of heat released by a gas burner of constant orifice. It indicates the quality of the gas and is given by the expression

21

V

Where:

V = the gross calorific value in BTU per cubic foot at STP

= specific gravity.

Appendix B Blank wiring schedule

7951 (APPX-B /AC) Page B.1



Page B.2 7951 (APPX-B /AC)

Appendix C Technical data for the 7951

7951 (Appx-C/CA) Page C.1


C.1 What this Appendix contains Ordering information – understanding model codes.

List of different types of external connections you can make to 7951.

Technical Specification.

Rear panel connector diagrams and pin identity tables.

Internal earthing arrangements.

C.2 Ordering information Note: To find out the exact model you have, locate the model code on the rear panel, then use this table.

Code Product 7951EA 7951Flow Computer

Code Rear Panel A Klippon connector 1, 2 4 analog i/p’s as standard (8 analog inputs if option 8 below) B D-type connectors 1, 2 4 analog i/p’s as standard (10 analog inputs if option 8 below)

Code Software Application 4

1 Gas applications – 1510 Single-Stream Flow Computer software 2 Gas applications – 1520 Dual-Stream Flow Computer software 6 Liquid applications – 2510 Single-Stream Flow Computer software

Code Communication Ports 3 Three serial communications ports Code Analog Inputs and Outputs 2

4 4 analog inputs, and 4 analog outputs 8 8 (Klippon) OR 10 (‘D’-type) analog inputs, and 4 analog outputs Code Option Boards N None H 2 channel HART board Code Connector kits for use with 25-way D-type connectors 3

N No commector kits required 5 5 connector kits for use with 7951EAB Code Configuration Tool N Not required B PC Config + Serial Communications Cable 7951EA A 1 3 4 N N B (Typical Model Code)

(1) 7951EA A has 1 dual-pulsed flowmeter input. For dual-stream applications with pulsed flowmeter inputs, use option B.

(3) For liquid proving, ‘D’-type connectors and extra analog I/O (option 8) must be specified.

(3) Connector kits are not needed with Klippon connectors (option A), but they are recommended with D-type connectors (option B).Each kit includes a 1.8m cable, and a DIN rail-mounted connector block with screw terminals.

(4) Software supplied will be latest issue of software, unless otherwise specified on order.


Page C.2 7951 (Appx-C/CA)

C.3 External connections You can make the following types of external connections to the 7951:

INPUTS Analog Inputs from devices which monitor continuously changing parameters and transmit analog signals. These include:

PRTs (PT100)

temperature transducers (0/4-20mA)

pressure transducers (0/4-20mA)

differential pressure transducers (0/4-20mA)

Viscosity transducers (e.g. Covimat 0/4-20mA)

Calorimeters (0/4-20mA).

Pulse Inputs from devices which transmit information as pulses. For example, a turbine (or positive displacement) flowmeter.

Time period (Dens./Visc.)

Inputs from devices where the frequency of the transmitted signal is related to the parameter being measured. These include:

Density transducers (e.g. 7835 or 7826)

Base density transducers

Viscosity transducers (e.g. 7827).

Status One of two levels, to show the state of some part of the system, such as whether a valve is open or closed.

OUTPUTS Analog Outputs from the signal converter to those devices (such as chart recorders) which require analog outputs (0/4-20mA).

Pulse For equipment such as pulse summators or electro-mechanical totalizers (open collector).

Status Outputs to equipment whose status is to be changed as, for example, an output which opens or closes a valve (open drain).

SERIAL COMMUNICATIONS

For receiving and sending information to other devices linked to 7951. These include:

Printers.

Host computers.

Master or slave 7951s, Chromatographs, etc.



POWER SUPPLIES Inputs d.c. only

Outputs d.c. only. These provide power within the 7951 and to some other external devices such as transducers.

Isolation notes

The isolation between the enclosure and all DC power inputs, signal inputs and signal outputs is: 50VDC continuously OR 125VDC for less than 15 seconds.

Consequently, isolation between any two signal lines and any DC power line is:

100VDC continuously OR 250VDC for less than 15 seconds.

C.4 Maximum number of external connections The table below lists the maximum number of external connections which you can make to a single 7951.

Type of connection Maximum number

Standard Option 1 Extra I/O Option 2 Extra I/O

Klippon D-type Klippon D-type Klippon D-type

Inputs

Analogue (Non-SMART) 4 4 4 1 6 2 0 0

HART Analog (SMART) 0 0 0 0 2 3 2 4

Pulse 1 2 0 0 0 0

Time period 4 4 0 0 0 0

Status 6 10 0 8 2 0 0

Outputs

Analogue 4 4 4 1 4 2 0 0

Pulse 3 5 0 0 0 0

Status 6 9 0 8 2 0 0

Serial Communications

RS232 1 1 0 0 0 0

RS232/485 2 2 0 0 0 0

(1) Use ordering code 7951EAA*38N** for Klippon option 1 only, or 7951EAA*38H** for both Klippon options 1 and 2.

(2) Use ordering code 7951EAB*38N** for D-type option 1 only, or 7951EAB*38H** for both D-type options 1 and 2.

(3) Use ordering code 7951EAA*34H** for Klippon option 2 only, or 7951EAA*38H** for both Klippon options 1 and 2.

(4) Use ordering code 7951EAB*34H** for D-type option 2 only, or 7951EAB*38H** for both D-type options 1 and 2.



C.5 Specification

GeneralEnvironmental Working temperature 0 to +50°C (-4 to +158°F)

Storage temperature -20 to +70°C (-32 to 122°F)

Relative humidity Up to 90% non-condensing

Bump BS 2011 test Eb

Vibration Tested to IEC publication 68-2-6, Part II, frequency 10 to 150Hz, maximum acceleration 20m/s2

EMC Emissions and Immunity EN 61326-1998 industrial locations)

Safety To BS EN 61010 standards

Enclosure IP50 from the front panel, only when mounted.

Dimensions Height 101mm (3.98”)

Width 197mm (7.76”)

Depth 257mm (10.1”)

Weight 2.5kg (5.5lb)

External connections Type 7951EAA****** (Klippon): Klippon multi-way connector system for all signals except communications. Separate 9-way D-type connectors for communications.

Options 7951EAB******(D-type): 5x25-way D-type for all connections except communications and power. Separate 9-way D-type connectors for communications.4-way Klippon connector for power.



Inputs

Analog Quantity 4 off, each selectable as PRT (PT100) or 4-20mA

Options Option for extra 4-20mA inputs: 7951EAA*38*** (Klippon): 4 off 7951EAB*38*** (D-type): 6 off

Type 0/4 to 20mA

Span selection Unlimited (keyboard selectable)

Uncertainty without HART active ±0.008% of full scale at 25oC ± 0.001%/°C

Uncertainty (of inputs 5 & 6) with HART active

±0.1% of full scale at 25oC ± 0.001%/°C

Resolution 20-bit (1 part per million)

Sampling time 50ms per channel

(Temperature PRT) Using Analog Inputs 1 to 4.

Configuration 4-wire: Power return line connected to Analog Input GND

Temperature range -200°C to +220°C for 100 PRT

Uncertainty ± 0.05°C

Resolution ± 0.02°C

Sampling time 50ms per channel

Energisation <1mA average (Meets BS1904 & IEC751, <1mW in the PT100)

Long term drift <20ppm per 1000 hours for first 1000 hours, subsequently far less

(HART) Using Analog Inputs 5 to 6 (if 7951 has extra I/O option).

Number of variables 8 variables. Up to 2 HART loops. Point-to-point and Multu-drop support (each loop uses an analog input).

Sampling time 400 ms per active transmitter

Pulse Quantity 7951EAA****** (Klippon): 1 single/dual-pulse flowmeter.7951EAB******(D-type): 2 single/dual-pulse flowmeter.

Options None

Pulse integrity checking IP 252/76, API Ch 5.5 Level A

Pulse interpolation / Dual-pulse chronometry API MPMS Ch 4.6

Type Pulse count, maximum rise time 80ms

Input trigger level 0.5V RMS (1.2V p-p)

Max. voltage level 30V

Frequency range 0 to 5kHz (dual-pulse train), minimum pulse width 100 s0 to 10kHz (single-pulse train), minimum pulse width 50 s



Time period (Dens./Visc.) Quantity 4

Options None

Range 100 s to 5000 s

Accuracy ± 1ns typically, ± 10ns worst case

Resolution 2ns at 1kHz for 1-second sample

Input trigger level 0.5V RMS (1.2V p-p), Maximum 30V

Input impedance 10k nominal

Digital (Status) Quantity 7951EAA****** (Klippon): 6 off 7951EAB****** (D-type): 10 off

Options Option for extra status inputs: 7951EAA****** (Klippon): 0 off 7951EAB*38*** (D-type): 8 off

Input voltage required 5 to 24V per channel (opto-isolated)

Update rate 0.5ms for prove detect, others 250ms maximum.

Special Notices Status Inputs 1 and 2 are fleeting contact ball detectors for prover interface (opto-isolated). They can also be used as normal status inputs.

OutputsAnalog Quantity 4

Options Option for extra 4-20mA analogue outputs:

7951EAA*38*** (Klippon): 4 off

7951EAB*38*** (Klippon): 4 off

Type of output Current (powered by 7951)

Power One 24V supply with capacity for 8 outputs @ 25mA each.

Maximum loop impedence 1K

Type 0/4 to 20mA (selectable)

Zero offset 20% or 0% (keyboard selectable)

Span selection Unlimited (keyboard selectable)

Accuracy 12-bit (±0.075% of full scale)

Resolution 1 part in 3500

Output impedence 1M minimum

Output representation Any measured ot computed value (keyboard selectable)

Update rate 0.1 seconds minimum

Isolation All analog outputs are galvanically isolated from ground

Long term drift <20ppm per 1000 hours for first 1000 hours, subsequently far less



Special Notices 1. The maximum load impedance that the analog outputs can drive is 1K Ohms. This must include any barrier impedance and the load itself.

2. Analog outputs are “Active Loops”. (Active loops are powered by the device providing the current output. “Passive loops” are powered externally, usually by the device receiving the current)

Pulse Quantity 7951EAA****** (Klippon): 3 off 7951EAB****** (D-type): 5 off

Options None

Type Open-collector Darlington drivers

Output rating 200mA @ 24V with 50% duty cycle

Switch voltage 24V maximum

Maximum frequency 10Hz

Digital (Status) Quantity 7951EAA****** (Klippon): 7 off 7951EAB****** (D-type): 9 off

Options Option for extra status outputs:

7951EAA*38*** (Klippon): 0 off

7951EAB*38*** (D-type): 8 off

Type Output 1 is a relay (0.5 Amp DC), all others are FET open-drain

Rating 250mA @ 24V

Switching voltage 24V

Communications

Serial Communications Port 1 Physical layer RS232 full duplex

Max. baud rate 19K2

Handshake XON/XOFF

Port 2 Physical layer RS232 full duplex or RS485 half duplex

Max. baud rate 19K2

Handshake XON/XOFF and/or RTS/CTS

Port 3 Physical layer RS232 full duplex or RS485 half duplex

Max. baud rate 19K2

Handshake XON/XOFF and/or RTS/CTS

Software protocols Modbus ASCII, RTU (Master, Slave, and Peer). Data type IEEE 32 and 64-bit. 16-bit integers optional. Commands 03, 04, 06, and 16



Hardware facilities

Microprocessor Processor Motorola 68332

Clock speed 24 MHz

Computation resolution 64-bit (IEEE 754), fully-floating point maths package. Embedded Real-time operating system.

Computation accuracy < 1 part in 1011

Memory Program storage 2 Mbyte FLASH, field upgradeable using serial link and Winboot software tool

Data storage 2 Mbyte of RAM, battery-backed by internal Lithium cell (as used by real-time clock also).

Battery life is typically 2 years if 7951 is un-powered, or 5 years if powered.

16kB FRAM non-volatile store for calibration data

Options None

Keyboard interface Number of keys 30

Key scan time 2ms

Debounce 14ms

Options None

Display Number of lines 4

Characters per line 20 alpha numeric

Backlight LED, continuously powered

Contrast software selectable, temperature compensated

Options None

Real-time clock Accuracy 1 part in 90000

Power Replaceable Lithium button cell (CR2430)

Battery life is typically 2 years if 7951 is un-powered, or 5 years if powered.

Options None

Battery monitor Type ADC, indicates battery condition

Options None



Alarm annunciation Quantity 3 (one each for Input, System or Limit alarms)

Type Red LED

Operation Flash indicates new alarm condition. Steady indicates accepted alarm.

Options None

Security Mechanisms 1. Switch located on front panel 2. Software code

Indicator Bi-colour LED on the front panel: 1. RED: Not secured 2. GREEN: Secured 3. ORANGE: Part-secured

Options None

Power SuppliesInput 21V to 30V dc.

Unloaded: 20W maximum. Loaded: 35W maximum. 2A worst-case start-up current

Output General instrumentation energisation

1 x 24V nominal at 800mA

Flowmeter energisation Switchable voltages of 8V or 16V, current limited to 120mA

DAC energisation Isolated 25V output at 200mA

Options None



C.6 Connections C.6.1 7951 D-type Rear Panel

Pin PL1 SK1 SK2 SK3 SK4 SK5 SK6 SK7 SK8 1 E Com 2 Rx/Tx+ Com 3 Rx/Tx+ Stat ip 1 Stat op 2 Turb 1 + Ana op 1 PRT 3 pwr +

2 E Com 1 Tx Com 2 Tx Com 3 Tx Stat ip 2 Stat op 3 Turb 1 - Ana op 2 PRT 3 sig +

3 Supply - Com 1 Rx Com 2 Rx Com 3 Rx Stat ip 3 Stat op 4 Turb 2 + Ana op 3 PRT 3 sig -

4 Supply + Stat ip 4 Stat op 5 Turb 2 - Ana op 4 PRT 3 pwr -

5 Com 0V Com 0V Com 0V Stat ip 5 Stat op 6 Turb 3 + Ana op 5 PRT 4 pwr +

6 Stat ip 6 Stat op 7 Turb 3 - Ana op 6 PRT 4 sig +

7 Com 2 CTS Com 3 CTS Stat ip 7 Stat op 8 Turb 4 + Ana op 7 PRT 4 sig -

8 Com 2 RTS Com 3 RTS Stat ip 8 Stat op 9 Turb 4 - Ana op 8 PRT 4 pwr -

9 Com 2 Rx/Tx- Com 3 Rx/Tx- Stat ip 9 Stat op com Ana ip 5 +

10 Stat ip com Pulse op 1 Turb pwr + Ana op com Ana ip 5 -

11 Pulse op 2 Turb pwr + Ana op com

12 Alarm NO Pulse op 3 Turb pwr - Ana op com +24V dc

13 Alarm com Pulse op com Turb pwr - Ana op com 0V dc

14 Stat ip 10 Stat op 10 Den 1 + PRT 1 pwr + Ana ip 6 +

15 Stat ip 11 Stat op 11 Den 1 - PRT 1 sig + Ana ip 6 -

16 Stat ip 12 Stat op 12 Den 2+ PRT 1 sig - Ana ip 7 +

17 Stat ip 13 Stat op 13 Den 2 - PRT 1 pwr - Ana ip 7 -

18 Stat ip 14 Stat op 14 Den 3+ PRT 2 pwr + Ana ip 8 +

19 Stat ip 15 Stat op 15 Den 3 - PRT 2 sig + Ana ip 8 -

20 Stat ip 16 Stat op 16 Den 4+ PRT 2 sig - Ana ip 9 +

21 Stat ip 17 Stat op 17 Den 4 - PRT 2 pwr - Ana ip 9 -

22 Stat ip 18 Stat op com +24V dc Ana op com Ana ip 10 +

23 Stat ip com Pulse op 4 +24V dc Ana op com Ana ip 10 -

24 Pulse op 5 0V dc Ana op com +24V dc

25 Alarm NC Pulse op pwr 0V dc Ana op com 0V dc



C.6.2 7951 Klippon Rear Panel

Pin PL1 SK1 SK2 SK3 1 E Com 2 Rx/Tx+ Com 3 Rx/Tx+

2 E Com 1 Tx Com 2 Tx Com 3 Tx

3 Supply - Com 1 Rx Com 2 Rx Com 3 Rx

4 Supply +

5 Com 0V Com 0V Com 0V

6

7 Com 2 CTS Com 3 CTS

8 Com 2 RTS Com 3 RTS

9 Com 2 Rx/Tx- Com 3 Rx/Tx-

Pin PL2 PL3 PL4 PL5 PL6 PL7 PL8 PL9 1 Stat op 2 Pulse op +ve Turb A ip+ Den 1 ip + Ana op 1 PRT 1 pwr + PRT 3 pwr + 24V pwr +

2 Stat op 3 Pulse op 1 Turb A ip - Den 1 ip - Ana op 2 PRT 1 sig + PRT 3 sig + Ana ip 5 +

3 Stat op 4 Pulse op 2 Turb B ip + Den 2 ip + Ana op 3 PRT 1 sig - PRT 3 sig - Ana ip 5 -

4 Stat op 5 Pulse op 3 Turb B ip - Den 2 ip - Ana op 4 PRT 1 pwr - PRT 3 pwr - 24V pwr -

5 Stat op 6 Pulse op com Turb pwr + Den 3 ip + Ana op 5 PRT 2 pwr + PRT 4 pwr + 24V pwr +

6 Stat op 7 Stat ip 1 Turb pwr - Den 3 ip - Ana op 6 PRT 2 sig + PRT 4 sig + Ana ip 6 +

7 Stat op com Stat ip 2 Stat ip 5 Den 4 ip + Ana op 7 PRT 2 sig - PRT 4 sig - Ana ip 6 -

8 NO alarm Stat ip 3 Stat ip 6 Den 4 ip - Ana op 8 PRT 2 pwr - PRT 4 pwr - 24V pwr -

9 Com alarm Stat ip 4 Stat ip 7 24V pwr + Ana op com Ana ip 7 + Ana ip 8 + 24 V pwr +

10 NC alarm Stat ip com Stat ip 8 24V pwr - Ana op com Ana ip 7 - Ana ip 8 - 24V pwr -



C.6 EarthingIn addition to earthing the chassis, (described in chapter 4), you may have to make extra earth connections in some cases, depending on the installation requirements.

The types of connection can be split into three groups, each of which has different earthing requirements. The groups are:

Group 1 (non-isolated power supply): Serial communications ports. Pulse outputs. Status outputs.

Group 2 (isolated power supply): Status inputs.

Group 3 (isolated power supply): Analogue inputs. Frequency inputs. Analogue outputs.

The diagrams on the next two pages shows you how to earth the external connections.



E E 0v +24VDC Power

Protect Ground

Group 1Chassis and instrumentation

are earthed togetherunless you cut the link

Group 2No earthing is required

for Status Inputs

SK3

Link

PL2Chassis

Earth Earthstud

Group 3Connect external earths as

required.

Pin 1

Pin 9

Protect Ground

SK2

Pin 1

Pin 9

Protect Ground

CommonSK1

Pin 1

Pin 9

Common

Common

PL2Pin 10Pin 1

Status Outputs Common

PL9Pin 1

Pin 10

Analogue Power -

Density Power -Pin 1

Pin 10PL5

PL4

Turbine Power -

Pin 10

Pin 1

Internal Isolated Supply

PL6Pin 10Pin 1

Internal Isolated Supply

PL3Pin 10

Pin 1

Opto-isolator common only

PL3Pin 10

Pin 1

Pulse Outputs Common

SERIALPORT

PULSEOUTPUTS

STATUSOUTPUTS

STATUSINPUTS

ANALOGUEOUTPUTS

SERIALPORT

SERIALPORT

Figure C.1: Earthing arrangements for the 7951 (Klippon connectors)



Link

SK8

Analogue o/pCommon

E E 0v +24VDC Power

Analogue Power -

Protect Ground

Protect Ground

Protect Ground

Protect Ground

SK7

Group 1Chassis and instrumentation are earthed together unless

you cut the link

Group 2No earthing is

required for StatusInputs

Pin 1

Pin 25

SK3

PL1Chassis

Earth Earthstud

Group 3Connect external

earths asrequired.

SK6

Pin 1

Pin 25

Density Power -

Turbine Power -

Pin 1

Pin 25

Protect GroundSK4

Pin 1

Pin 25

Opto-isolator common only

Pin 1

Pin 9

Protect Ground

SK5

Pin 1

Pin 25

Status Output common

Pulse Output common

Protect Ground

SK2

Pin 1

Pin 9

Protect Ground

CommonSK1

Pin 1

Pin 9

Common

Common

STATUSINPUTS

SERIALPORT

PULSEand

STATUSOUTPUTS

SERIALPORT

SERIALPORT

Figure C.2: Earthing arrangements for the 7951 (D-type connectors)



Earthing requirements for group 1 connections only

In general, the earthing arrangements are different for large and small installations. (A small installation may possibly consist of just one instrument.)

If the 7951 is part of a large installation with separate earths for chassis and instrumentation:

In this case you may (depending on the overall system requirements) earth the 7951 chassis and instrumentation separately by cutting the link on the connector board.

If the 7951 is on its own or in a small installation with one common earth for chassis and instrumentation:

In this case you must leave the link intact so that the chassis and instrumentation are earthed to the same point.

LinkProcessorBoard

MotherBoard

RearPanel


SocketSK1

Figure C.3: Where to find the link on the connector board




The status inputs do not have to be earthed because the circuitry contains only opto-electrical components.


These depend on what sort of installation you have and the environment in which it operates. You therefore have to decide what earthing arrangements you need. It is likely that this group has to be earthed at a zener barrier earth. For further information, refer to the documentation for the external devices which are connected to the installation.




In general, the earthing arrangements are different for large and small installations. (A small installation may possibly consist of just one instrument.)

If the 7951 is part of a large installation with separate earths for chassis and instrumentation:

In this case you may (depending on the overall system requirements) earth the 7951 chassis and instrumentation separately by cutting the link on the connector board.

If the 7951 is on its own or in a small installation with one common earth for chassis and instrumentation:

In this case you must leave the link intact so that the chassis and instrumentation are earthed to the same point.

LinkProcessorBoard

MotherBoard

RearPanel


SocketSK1

Figure C.3: Where to find the link on the connector board




The status inputs do not have to be earthed because the circuitry contains only opto-electrical components.


These depend on what sort of installation you have and the environment in which it operates. You therefore have to decide what earthing arrangements you need. It is likely that this group has to be earthed at a zener barrier earth. For further information, refer to the documentation for the external devices which are connected to the installation.

Appendix D Units and conversion factors

7951 (Appx-D /AD) Page D.1

Appendix D Units and conversion factors The figures in the following table are taken from BS 350: Part 1: March 1974.

Parameter Imperial units Metric equivalent

Length 1 inch 1 foot

25.4 mm 0.3048 m

Mass 1 lb 1 ton

0.45359237 kg 1016.05 kg

Density 1 lb/ft3

1 lb/gal 1 lb/US gal

16.0185 kg/m3

99.7763 kg/m3

119.826 kg/m3

Pressure

1 lb/in2

1 atm 1 MPa 1 N/m 1 mm Hg (0o)1 in Hg (0o)

68.9476 mbar 1.013250 bar 10 bar 10-5 bar 1.33322 x 10-3 bar 33.8639 x 10-3 bar

Volume or capacity

1 in3

1 ft3

1 gal 1 US gal 1 US barrel

16.8371 cm3

0.0283168 m3

4.54609 dm3

3.78541 dm3

0.158987 m3

Volume flow 1 ft3/min 1 gal/min

40.776 m3/day6.5463 m3/day

Mass flow 1 lb/hr 1 ton/hr

10.886 kg/day 1016.05 kg/hr

Energy 1 BTU 1 kWh 1 therm

1.05506 kJ 3.6 MJ 105.506 MJ

Temperature oF (1.8 x oC) + 32

Viscosity (dynamic) 1 P 1 lbf/(ft s) or 1 pdl s/ft2

1 slug/(ft s) or 1 lbf s/ft2

0.1 Pa s 1.48816 Pa s 47.8803 Pa s

Viscosity (kinematic) 1 St 1 ft2/s

1 cm2/s 9.29030 dm2/s

Appendix D Units and conversion factors

Page D.2 7951 (Appx-D /AD)

Appendix E Data tables

7951 (AppxE/AD) Page E.1


E.1 The tables Note: The equations used to derive these tables are given in Section E.2.

Density/temperature relationship of crude oil

Temp.(°C) Density (kg/m3)

60 738.91 765.06 791.94 817.15 843.11 869.01 894.86 920.87 946.46 55 742.96 768.98 794.93 820.83 846.68 872.48 898.24 923.95 949.63 50 747.00 772.89 798.72 824.51 850.25 875.94 901.80 927.23 952.82 45 751.03 776.79 802.50 828.17 853.81 879.40 904.96 930.50 956.00 40 755.05 780.68 806.27 831.83 857.36 882.85 908.32 933.76 959.18 35 759.06 784.57 810.04 835.48 860.90 886.30 911.67 937.02 962.36 30 763.06 788.44 813.79 839.12 864.44 889.73 915.01 940.28 965.53 25 767.05 792.30 817.54 842.76 867.97 893.16 918.35 943.52 968.89 20 771.03 796.18 821.27 846.38 871.49 896.59 921.68 946.77 971.85

15.556 774.56 799.57 824.59 849.60 874.61 899.62 924.63 949.64 974.65 15 775.00 800.00 825.00 850.00 875.00 900.00 925.00 950.00 975.00 10 778.95 803.83 828.72 853.61 878.50 903.41 928.32 953.23 978.15 5 782.90 807.65 832.42 857.20 882.00 906.81 931.62 958.45 981.29 0 786.83 811.46 836.12 860.79 885.49 910.21 934.92 959.66 984.42

Density/temperature relationship of refined products

Temp.(°C) Density (kg/m3)

60 605.51 657.32 708.88 766.17 817.90 868.47 918.99 969.45 1019.8755 610.59 662.12 713.50 769.97 821.49 872.00 922.46 972.87 1023.2450 615.51 666.91 718.11 773.75 825.08 875.53 925.92 976.28 1026.6045 620.49 671.68 722.71 777.53 828.67 879.04 929.38 979.69 1029.9640 625.45 676.44 727.29 781.30 832.24 882.56 932.84 983.09 1033.3235 630.40 681.18 731.86 785.86 835.81 886.06 938.28 986.48 1038.6730 635.33 685.92 736.42 788.81 839.37 889.56 939.72 989.87 1040.0125 640.24 690.63 740.96 792.55 842.92 893.04 943.16 993.26 1043.3520 645.13 695.32 745.49 796.28 846.46 896.53 946.58 996.63 1046.68

15.556 649.46 699.48 749.50 799.59 849.61 899.61 949.62 999.63 1049.6315 650.00 700.00 750.00 800.00 850.00 900.00 950.00 1000.00 1050.0010 654.85 704.66 754.50 803.71 853.53 903.47 953.41 1003.36 1053.325 659.67 709.30 758.97 807.41 857.04 906.92 956.81 1006.72 1056.630 664.47 713.92 763.44 811.10 860.55 910.37 960.20 1010.07 1059.93

The two tables above are derived from equations in the Revised Petroleum Measurement Tables (IP 200, ASTM D1250, API 2540 and ISO R91 Addendum 1).


Page E.2 7951 (AppxE/AD)

Platinum resistance law (To DIN 43 760)

°C Ohms °C Ohms °C Ohms °C Ohms °C Ohms

-220 10.41 -120 52.04 -20 92.13 80 130.89 180 168.47

-210 14.36 -110 56.13 -10 96.07 90 134.70 190 172.16

-200 18.53 -100 60.20 0 100.00 100 138.50 200 175.8

-190 22.78 -90 64.25 10 103.90 110 142.28 220 183.17

-180 27.05 -80 68.28 20 107.79 120 146.06 240 190.46

-170 31.28 -70 72.29 30 111.67 130 149.82 260 197.70

-160 35.48 -60 76.28 40 115.54 140 153.57 280 204.88

-150 39.65 -50 80.25 50 119.40 150 157.32

-140 43.80 -40 84.71 60 123.24 160 161.05

-130 47.93 -30 88.17 70 127.07 170 164.76

Density of ambient air (in kg/m3) at a relative humidity of 50%

Air Pressure

Air Temperature (°C)

(mb) 6 10 14 18 22 26 30

900 1.122 1.105 1.089 1.073 1.057 1.041 1.025 930 1.159 1.142 1.125 1.109 1.092 1.076 1.060 960 1.197 1.179 1.162 1.145 1.128 1.111 1.094 990 1.234 1.216 1.198 1.180 1.163 1.146 1.129

1020 1.271 1.253 1.234 1.216 1.199 1.181 1.163

Density of pure water (in kg/m3

to ITS - 90 Temperature Scale) Temp

°C 0 2 4 6 8 10 12 14 16 18

0 999.840 999.940 999.972 999.940 999.848 999.699 999.497 999.244 998.943 998.595 20 998.203 997.769 997.295 996.782 996.231 995.645 995.024 994.369 993.681 992.962 40 992.212 991.432 990.623 989.786 988.922 988.030 987.113 986.169 985.201 984.208 60 983.191 982.150 981.086 980.000 978.890 977.759 976.607 975.432 974.237 973.021 80 971.785 970.528 969.252 967.955 966.640 965.305 963.950 962.577 961.185 959.774

100 958.345



Velocity of Sound in Liquids The values for a selection of fluids are given below. You can obtain further details from reference books such as Tables of Physical and Chemical Constants and some Mathematical Functions by G W C Kaye and T H Laby.

Liquid Temperature (t °C)

Velocity of Sound ( c ) ms-1)

Rate of Change ( t/c ms-1K-1)

Acetic acid 20 1173 ----

Acetone 20 1190 -4.5

Amyl acetate 29 1173 ----

Aniline 20 1656 -4.0

Benzine 20 1320 -5.0

Blood (horse) 37 1571 ----

Butyl acetate 30 1172 -3.2

Carbon disulphide 25 1142 ----

Carbon tetrachloride 20 940 -3.0

Chlorine 20 850 -3.8

Chlorobenzene 20 1290 -4.3

Chloroform 20 990 -3.3

Ethanol amide 25 1724 -3.4

Ethyl acetate 30 1133 -3.9

Ethyl alcohol 20 1162 -3.6

Formic acid 20 1360 -3.5

Heptane 20 1160 -4.5

n-Hexane 30 1060 ----

Kerosene 25 1315 -3.6

Menthol 50 1271 ----

Methyl acetate 30 1131 -3.7

Methyl alcohol 20 1121 -3.5

Methylene Chloride 25 1070 ----

Nitrogen -189 745 -10.6

Nonane 20 1248 ----

Oil (castor) 19 1500 -4.1

Oil (olive) 22 1440 -2.8

Octane 20 1197 ----

Oxygen -186 950 -6.9

n-Pentane 20 1044 -4.2

n-Propyl acetate 26 1182 ----

Toluene 20 1044 -4.2

Turpentine 25 1225 ----

Water (distilled) 10 1447.2 ----

20 1482.3 ----

30 1509.1 ----

50 1542.5 ----



Water (sea) -4 1430.2 ----

00 1449.5 ----

05 1471.1 ----

15 1507.1 ----

25 1534.7 ----

o-Xylene 22 1352 ----



E.2. Equations used to derive data tables Density/temperature relationship The density/temperature relationship is:

where: t = density at line temperature t°C (kg/m3)

15 = density at base temperature 15°C (kg/m3)

t = t°C -15°C (i.e. t - base temperature)

15 = tangent thermal expansion coefficient per °C at base temperature 15°C

Tangent thermal expansion coefficient The tangent thermal expansion coefficient differs for each of the major groups of hydrocarbons. It is obtained from the equation:

Product compressibility The definition of compressibility used to develop the table in Section 1 of the IP Petroleum measurement Manual is the isothermal secant compressibility, defined by the equation:

T2121

0 PPVV

V1

Where: = isothermal secant compressibility at temperature T

0V = volume of liquid at atmospheric pressure

1V = change in volume from 0V to 1V

2V = change in volume from 0V to 2V

1V & 2V = volumes at pressures 1P and 2P , respectively

1P & 2P = gauge pressure readings (Bar)

t15t1515t 8.01exp

215

151015

KK

Where 0K and 1K are API factors which are obtained from the table:

Product Density Range

(kg/m3)

0K 1K

Crude Oil 771 - 981 613.97226 0.00000 Gasolines 654 - 779 346.42278 0.43884

Kerosines 779 - 839 594.54180 0.00000

Fuel Oils 839 - 1075 186.96960 0.48618



For practical purposes, when the liquid volume changes from 0V to 1V as the gauge pressure changes

from zero (atmospheric) to 1P , the above equation is simplified to:

T11

0 PV

V1

ISO Document TC 28/SC3/N248, (Generation of New Compressibility Tables for International Use) gives the following equations relating to the compressibility data:

eee logT0161654.0log02909.3T00343804.038315.1Clog

and

16 bar10C

Where: T = oil temperature in °C

r = oil density in kg/litre at 15°C

The new equation (from the API Manual of Petroleum Measurement Standards, Chapter 11.2.1M) gives (after converting to units of kg/m and bar):

1

10t2092.41087096.0t00021592.062080.14 bare10 15

2

3

152

6

Where: T = temperature in °C

r15 = density (in kg/m3) at 15°C and at atmospheric pressure

This equation is valid for the density range of 638 kg/m3 to 1074 kg/m3. For a density range of 350 kg/m3 to 637 kg/m3 refer to Chapter 11.2.2M in the API Manual.

Velocity of sound in liquids The velocity of sound in dilational waves in unbound fluids is given by:

21

ac

Where: c = velocity of sound

a = adiabatic compressibility

= density

Appendix F Calculations and theory

7951 2510 (AppxF/BC) Page F.1


Liquid viscosity measurement This is obtained from the equation:

42

21

0Q

V

Q

VVV

Where: = Fluid dynamic viscosity (cP).

V = Viscosity scaling factor.

0V = Viscosity coefficient from calibration certificate.



Q = Transducer quality factor.

Kinematic viscosity This is obtained from the equation:

U1000KV

Where: = Kinematic viscosity

= Fluid dynamic viscosity (cP)

V = Viscosity scaling factor

K = Density scaling factor

= Line density

Saybolt viscosity This is obtained from the equation:

532 10646.197.237.2622.3930

03264.00.16324.4100t000061.00.1.V.S

Where: t = Temperature in oF

= Kinematic viscosity in cSt.


Page F.2 7951 2510 (AppxF/BC)

Liquid density This is obtained from the equation:

2B2B10 KKK

Where: = Uncorrected density (kg/m3

0K = Density coefficient from calibration certificate



B = Periodic time B ( S)

Correction for operating temperatures other than 20oCThis is obtained from the equation:

20tK20tK1 1918t

Where: = Uncorrected density (kg/m3

1 = Density corrected for temperature



t = Line temperature in oC

Correction for high fluid viscosity This is obtained from the equation:

422

221

20tQ

K

Q

KK

Where: = Density corrected for viscosity

t = Density corrected for temperature




Q = Averaged quality factor of transducer.



Density/temperature relationship Correction factors in the revised API-ASTM-IP petroleum measurement tables are based on the equation:

t15t1515t 8.01exp

Where: t = Density at line temperature toC

15 = Density at base temperature 15oC

t = Line temperature-base temperature

15 = Tangent thermal expansion coefficient per oC at base temperature 15oC

The tangent thermal coefficient differs for each of the major groups of hydrocarbons. It is obtained from the equation:

215

15105

KK

Where: 15 = Density at line temperature toC

15 = Density at base temperature 15oC

0K = API factor

1K = API factor

Density/pressure relationship Isothermal secant compressibility is defined by the equation:

11

0 PV

V1

Where: = Isothermal secant compressibility at temperature toC

1V = Change of volume from 0V to 1V1P = Gauge pressure reading (P-1.103) bars

The correlation equation for from the available compressibility data is:

eee logt0161654.0log02909.3t00343804.038315.1Clog

Where: = Cx10-5 bar

t = Temperature in oC

= 1000

15 = oil density at 15oC (kg/litre).



Special calculation equation 1 The equation is:

fYedXcbaBAR

Where: R = Extra functions result

A , B = Constants

a - f = Pointers

X , Y = Constants


2CtBtAeR

Where: R = Result of special calculation 2

A , B , C = Constants

t = Pointer


155.27350155.273t*logA85.0log*log5.332.19V 10av101050

Where: t = Line temperature

av = Average kinematic viscosity

A = User-defined constant (it has a default value of 118)

85.010V

5.3350V

10

t

Where: = User-defined constant

tV = Viscosity at temperature t



Dynamic Viscosity The dynamic viscosity ( ) of a Newtonian fluid is given by: dr/dv

Where: = shearing stress between two planes parallel with the direction of flow

dr/dv = velocity gradient at right angles to the direction of flow.

The dimensions of dynamic viscosity are M L-1 T-1 and the SI unit is Pascal seconds (Pa s).

Dynamic ViscosityThe kinematic viscosity ( ) is the ratio of the dynamic viscosity to the density

The dimensions of kinematic viscosity are L2 T-1 and the SI unit is square metres per second (m2/s).

7951 Flow Computer

Operating ManualHB512510June 2009

The Emerson logo is a trade mark and service mark of Emerson Electric Co. All other marks are the property of their respective owners. We reserve the right to modify or improve the designs or specifications of product and services at any time without notice. International: Emerson Process Management Remote Automation Solutions Outgang Lane Pickering North Yorkshire, YO18 7JA United Kingdom Tel: +44 (0) 1751 471800 Fax: +44 (0) 1751 471801 www.emersonprocess.com/remote

Liquid Flow Computer Manual (2510 software)...7.7.1 Introduction 7.16 7.7.2 Worked Examples 7.17...

Documents

Transcript of Liquid Flow Computer Manual (2510 software)...7.7.1 Introduction 7.16 7.7.2 Worked Examples 7.17...