Volume 5d

Volume 5 Compendium of Technical Bulletins
COMPENDIUM OF TECHNICAL BULLETINS
Contents of Volume 5
Technical Bulletins in Volume 5
960701 Overview of OmniCom Configuration PC Software
960702 Communicating with Allen-Bradley Programmable Logic Controllers
960703 Storing Archive Data within the Flow Computer
960704 Communicating with Honeywell ST3000 Smart Transmitters
970701 Stability Requirements: Final Calibration of Flow Computer
970702 Secondary Totalizers Provide Net Volume at Temperatures Other than
15°C or 60°F
970801 Using Boolean Statements to Provide Custom Alarms in the Flow
Computer
970802 Omni Flow Computer Modbus Database: Overview
970803 Meter Factor Linearization
970804 Calculation of Natural Gas Net Volume and Energy: Using Gas
Chromatograph, Product Overrides or Live 4-20mA Analyzer Inputs of
Specific Gravity and Heating Value
970901 Dual Pulse Flowmeter Pulse Fidelity Checking
980201 Communicating with Honeywell TDC3000 Systems
980202 Recalculating a Previous Batch within the Flow Computer
980401 Peer-to-Peer Basics
980402A Using the Peer-to-Peer Function in a Redundant Flow Computer
Application
980501 Rosemount 3095FB Multivariable Sensor Interface Issues
All Revs 05/07 i

OMNI 6000/Omni 3000 User Manual Contents of Volume 5
Technical Bulletins in Volume 5 (Continued)

980502 Communicating with Honeywell™ SMV3000 Multivariable Transmitters
980503B Serial I/O Modules: Installation Options
980504 Multivariable Flow Transmitter Interfaces: Serial Connectivity and Data
Transfer Issues
980701 Using the Totalizer Maintenance Mode
980801 Unsolicited Transmissions of Custom Modbus™ Data Packets
980802 Digital I/O Modules: Installation Options
980803B Upgrading the Flow Computer Firmware
981101 Using the Audit Trail (Event Logger) Feature and Sealing of the Flow
Computer
990101B Communicating with Instromet® Ultrasonic Gas Flowmeters
000314B Connecting An Omni 3000/6000 with An Invensys Auto-Adjust Turbine
Meter
010701B Communicating with Kongsberg Metering MPU 1200 Ultrasonic Gas
Flowmeters
020101H OMNI Serial/Ethernet-Modbus Mux Module Model 68-6209: Setup &
Installation
020501 Communicating with Daniel Ultrasonic Gas Flowmeter Model 3400,
SeniorSonic
060327 Operating the SuitCase Prover Bi-Directional Pipe Configuration
060401 Communicating with SICK Ultrasonic Gas Flow Meter Flowsic 600
060419 OMNI 3000/6000 Totalizer Functions

060801 Understanding OMNI Flow Computer Time Synchronization
ii All Revs 05/07

Omni Flow Computers, Inc.
Last Updated: 05 05 2003 TB # 960701
Overview of OmniCom Configuration PC

Software
Contents
User Manual Reference - Scope ................................................................................................................... 2
This technical bulletin
complements the Abstract ............................................................................................................... 2
information contained in Configuring the Flow Computer........................................................................ 2
Volume 3, Chapter 2 “Flow
Computer Configuration”, Report Configurator ........................................................................................... 3
and is applicable to all
firmware revisions. Operations Utilities and Help............................................................................. 3
This bulletin was previously Dial-up Access .................................................................................................... 3
published as an appendix to
user manuals of firmware Passwords Using OmniCom ............................................................................. 3
revisions Version .70 and
Local Keypad Access .................................................................................................... 4
earlier.
Changing Passwords at the Keypad.............................................................................. 4
Setting Up the Initial 'Level B' and 'Level C' Passwords for each Modbus Port ............. 5
OmniCom Configuration Maintaining the Modbus Port Password Using OmniCom ........................................... 5
PC Software - This
powerful software package Disabling Modbus Port Passwords ................................................................................ 6
allows you to setup, copy or Getting Started .................................................................................................... 6
modify, and save to disk
entire configurations for Installation Requirements .............................................................................................. 6
Omni flow computers. It also Installation Procedure.................................................................................................... 6
allows you to create custom Opening a File ............................................................................................................... 7
reports and displays. You
can work online, offline and View .............................................................................................................................. 7
remotely. Off-line........................................................................................................................... 7
On-line........................................................................................................................... 7
Reports.......................................................................................................................... 8
Utilities........................................................................................................................... 8
I/O Point Assignment List............................................................................................................ 8
OmniCom Setup....................................................................................................................... 8
OmniCom Application ............................................................................................................... 9
Archive Start/Stop Command ..................................................................................................... 9
Prover Commands .................................................................................................................... 10
Diagnostics ............................................................................................................................... 10
Omni Front Panel Emulator ...................................................................................................... 10
Help............................................................................................................................. 10
Registration of License and Software Support ............................................................ 11
TB-960701 ALL REVS 1

Omni 6000 / Omni 3000 Flow Computers Technical Bulletin
Scope
OmniCom Software is compatible with all firmware revisions of Omni
6000/Omni 3000 Flow Computers. It is installed in a personal computer from
which you can configure your flow computer.
Abstract
OmniCom is a simple-to-use yet sophisticated PC-based configuration program
that can be used to setup, copy or modify, and save to disk entire configurations
Getting Tech Support -
Technical support is
for Omni flow computers. You can also select custom report options and modify
available at: report templates and Omni display screens that are resident within the program,
(281) 240-6161 or create new ones. These can then be uploaded to the flow computer. Default
Email should be sent via reports provide standard data and formats for most requirements.
the WEB Page at:
Major application programming has already been developed by Omni and is
www.omniflow.com resident in EPROM. This is of particular importance in custody transfer
or email to: measurement contracts. They require that the relevant API, AGA, GPA or ISO
techsupport@omniflow.com standards are fully implemented and not exposed to tampering.
The OmniCom program allows you to develop your own system requirements by
a simple process of menu selection and table completion. This replicates the
data entry tables which can be accessed through the front panel keypad of your
Omni Flow Computer.
Configuring the Flow Computer

Configuring the flow computer involves specifying what transducers are going to
be used, their calibrated ranges and the physical I/O points being assigned.
Other data needed by the flow computer relates to the flowing product to be
measured, the type of calculations to be used, and communication and control
features.
You will usually configure the flow computer in the Off-line Mode and then
upload your data. You do not have to be connected to the flow computer at this
time. You will usually go to the Online Menu only when you need to
communicate directly with the flow computer. Any changes made are
immediately reflected in the flow computer.
2 TB-960701 ALL REVS

TB-960701 Overview of OmniCom Configuration PC Software
Report Configurator
One of OmniCom's indispensable features is the ability to reformat default
reports by using OmniCom's report templates. This is the ONLY feature not
available through the front panel keypad. Any variable defined in the Modbus
database, or programmed as a variable can be inserted into a report with
accompanying text. Reports can be created in languages other than English to
suit local needs.
Operations Utilities and Help

Accessing Help in Operational tools such as remotely proving meters, and reading hardware
OmniCom - At the 'Using diagnostics are provided. Diagrams are also provided for communications cable
Help' feature, press [Enter] hook-up. Application Programs and PC Setup for OmniCom can also be
and [F1] for editing
keystrokes. selected. As you work through the entries, you will find entry-sensitive Help that
explains the meaning of the particular entry. Whether at the flow computer
keypad or at a PC there is always assistance.
For Further Help - If you
require further help, call
Dial-up Access
Omni’s technical support at:
+1-281-240-6161
Omni Flow Computers encourages the installation of a telephone dial-up

modem as a ready means of providing installation and maintenance support for
customer and vendor alike. Serial communication passwords provide enhanced
security. Three levels of password pre-exist within Omni flow computers to
provide privileged or restricted access to critical configuration and calibration
data.
The OmniCom program allows you to upload/download data to and from the
flow computer in an on-line mode at a range of baud rates by direct-wire or by
telephone dial-up modem access. This is particularly useful when the flow
computer is in use. Occasionally, you will want to modify configuration or
calibration data, or just monitor activity. You can do all this without interfering
with pipeline or process operations or with communication links to host SCADA
or DCS systems.
Passwords Using OmniCom

Except when changing transducer high/low alarm limits, a password is usually
asked for when changing the configuration data within the computer.
The flow computer has independent password protection of the following:
INFO - For Firmware 1) Local Keypad access
Revisions 70+, Physical
Serial Port #1 is selectable 2) Modbus Port #1 (Physical serial Port #1)
as a Modbus RTU, Modbus 3) Modbus Port #2 (Physical serial Port #2)
RTU (modem), or printer
port. This serial port on 4) Modbus Port #3 (Physical serial Port #3)
previous revisions was only 5) Modbus Port #4 (Physical serial Port #4)
a printer port.

Local Keypad Access

Three password levels are provided:
a) Privileged Level - Allows complete access to all entries within the flow
computer including keypad passwords (b) and (c) below. The initial
privileged password for each Modbus port is selected via this password
level.
b) Level 1 - This level allows technician access to most entries within the
flow computer with the exception of I/O Points assignments,
programmable variables and Boolean statements.
c) Level 1A - Allows access to the following entries:
♦ Meter factors and K Factors
♦ Densitometer correction factors (pycnometer factor)
d) Level 2 - Allows access to the operator type entries. These entries
include:
♦ Transducer manual overrides
♦ Product gravity overrides
♦ Prover operations
♦ Batching operations
Changing Passwords at the Keypad

1) At the keypad press [Prog] [Setup] [Enter]
2) With the cursor blinking on 'Misc Configuration' press [Enter]
3) With the cursor blinking on 'Password Main?'
press [Alpha Shift] [Y] [Enter]
4) Enter the 'Privileged Level' Password (up to 6 characters) press [Enter]
5) The 'Level 1',Level 1A and 'Level 2' passwords can now be viewed and
changed if required.
INFO - Level B and Level C 6) Scroll down to access each of the Modbus serial port 'Level A'
passwords for each Modbus passwords. These are labeled 'Ser1Passwd', Ser2 Passwd', 'Ser3
port cannot be viewed or
changed from the keypad.
Passwd' and ‘Ser4 Passwd’ corresponding to the physical port numbering
for Modbus Ports 1, 2, 3 and 4 respectively.

Setting Up the Initial 'Level B' and 'Level C' Passwords

for each Modbus Port
1) Enter an initial 'Level A' Password for the appropriate physical serial port
at the keypad of the Omni Flow Computer as described above.
2) Connect a PC running OmniCom Software to the selected serial port of
the Omni Flow Computer. Open a file and 'Receive Omni Configuration
Data'.
3) A red pop-up screen will appear which notes that a password is required
to proceed. If any other screen appears at this point, check wiring and
communication settings, Modbus ID, baud rate, etc.
4) Do not enter the 'Level A' password at this point. Keep pressed [Alt] as
you press [E] to edit the passwords. A second red pop-up screen will
appear asking for the 'current valid password'. A good practice would be
to use uppercase letters (activate [CapsLock] on the keyboard) because
when setting passwords from the flow computer’s keypad, they are
always entered in uppercase.
5) Enter the 'Level A' password that was selected for this serial port.
6) You are asked if you would like to change the 'Level A', 'Level B' and
'Level C' passwords. Select to change 'Level B' at this point. You will be
asked to enter a password. As you enter the password, asterisks will
show in place of the characters you typed. You will be asked to re-enter
the password to ensure that what you typed was correct.
7) To setup a ‘Level C’ password, repeat Steps 2 and 6 substituting ‘Level
C’ for ‘Level B’ at Step 6.
Maintaining the Modbus Port Password Using OmniCom

After the initial passwords have been setup for each of the Modbus serial ports
as shown above, they may be changed at any time while logged on with
OmniCom.
1) While keeping pressed the [Alt] key, press [E] at any time and the pop-
up screen appears asking for a password. This screen can be forced to
appear by keeping pressed [Ctrl] [Alt] as you press [P] while viewing
any editing screen; i.e., any screen with data fields that can be edited.
2) When asked, enter your current password. Password ‘Level B’ and
‘Level C’ users are allowed to change only their own password levels.
‘Level A’ password users can change levels A, B and C.

Disabling Modbus Port Passwords

INFO - Level B and Level C ‘Level B’ and ‘Level C’ passwords should be disabled via OmniCom (see
passwords for each Modbus sidebar) before disabling the privileged ‘Level A’ password at the keypad.
(serial) port cannot be
viewed or changed from the 1) To disable each password proceed as though you are going to change
keypad; i.e., you must use or set-up the password.
OmniCom to view, change
or delete these password 2) Press the [Delete] key six (6) times where the initial password was
levels.
entered followed by the [Enter] key (no asterisks will show).
3) When asked to re-enter the password, re-enter six [Delete] key presses
followed by the [Enter] key.
4) Repeat this procedure for both ‘Level B’ and ‘Level C’ passwords.
5) From the Omni flow computer keypad, delete the 'Level A' password for
the appropriate Modbus serial port (see Volume 3). To do this, move the
cursor to the serial Level A password to disable and press the [Clear]
key and then the [Enter] key.
Getting Started
CAUTION!
Installation Requirements
Terminate and Stay
Resident (TSR) programs To properly run OmniCom, and have sufficient memory for report templates and
such as SideKick and copies of the database, you will require the following:
Keyboard Macro processors
can affect the operation of ♦ IBM PC (or compatible)
high speed communication
programs such as ♦ MS DOS, V3.3 or later (excepting 4.01)
OmniCom. They do this by
'stealing' processor cycles ♦ 640Kb RAM
or turning off the hardware ♦ 20Mb Free Hard Disk Space with a minimum of one floppy disk drive, 3½"
interrupt system of the
personal computer. These 1.44 Mb
programs may have to be ♦ Monochrome or color monitor with EGA or VGA graphics capability
disabled when you are in
the 'On-line' Mode, if you ♦ One RS-232 serial port
encounter difficulties
communicating with the ♦ One LPT port (optional)
Omni flow computer. ♦ One RS-232 modem (optional at various supported baud rates)
Installing OmniCom
Revisions Previous to 70 -
Installation Procedure
Before you install earlier
revisions of OmniCom
OmniCom is delivered on 1.44 Mb, 3½" diskettes in an archived format. To
software, you must save install, do the following:
your existing phone
directory entries and setup.
For instructions and any 1) Insert the diskette into your PC's corresponding floppy disk drive.
other assistance you may
need, please contact our 2) Type the respective drive letter followed by a colon (e.g.: A: or B:).
technical support staff at the
following phone number:
3) Type Install and press [Enter].
+1-281-240-6161
The OmniCom installation program will guide you through the rest of the
installation.

Opening a File
Accessing Help in First open an existing Omni-supplied file. Each application and derived files
OmniCom - At the 'Using come with their own set of templates. You can then 'SAVE AS' to create a new
Help' feature, press [Enter] file to commence your configuration. Each file that you create will occupy
keystrokes. approximately 60 Kbytes of disk space. This includes 36 Kbytes for the
configuration file and 6 Kbytes for each of the four custom report templates.

All menu selections are supported by entry-sensitive ‘Help’. No matter where
require further help, call you are, by pressing [F1] you can obtain an explanation of the requirements for
Omni’s technical support at: your entry selection.
+1-281-240-6161
View
Files can be viewed separately or in parallel with a file that is currently being
edited. This allows you to compare various numeric entries in similar files. This
can be helpful if you are maintaining historical files that track changes you have
made. You may not be able to use the ‘View’ feature with certain variations of
flow computer configuration files because newer firmware include additional
entry fields not available in earlier revisions.
Off-line
You will usually begin in the Off-line Mode to configure your flow computer. It
naturally leads in to the 'Omni Configuration' Menu selections. Only when you
complete this section will you be able to activate the various 'Setup' options and
proceed to establish your calibration ranges and other related data. Before you
begin the configuration of I/O, be sure you know what number and type of
physical I/O has been installed in the flow computer. A mismatch between your
off-line configuration and physical hardware will not make a data upload to the
flow computer meaningful in key areas of your configuration data.
On-line
When you have completed building your configuration database, you are then
ready to upload data to your Omni flow computer. The OmniCom program uses
the Modbus RTU binary protocol which mandates the use of 8 data bits. Be
sure that the serial I/O parameters in both devices have been properly setup
before attempting to communicate. Baud rate and parity settings are less critical
but must also be the same.
With a direct-connect to a PC, OmniCom will perform an auto baud rate search
and display an error if baud rates are incompatible (see 2.5.16. Serial
Input/Output Settings in Volume 3). Baud rates from 1.2 kbps to 38.4 kbps are
supported. When using a modem, the auto baud rate search is not performed.
In this case, the baud rate is that at which the modem is setup. Some personal
computers may not have the processing power to support the higher baud rates.
Note also that modems are capable of using a higher baud rate at the RS-232
connector than they are communicating on the telephone line. If the modems
connect but the flow computer does not respond, try adjusting the flow
computer’s baud rate.

Reports
The 'Report' Menu allows you to retrieve snapshot and historical reports from
the flow computer or from your hard disk. These are pre-formatted default
reports that are included in the Omni application software. You can also
customize your own reports from standard templates. By using the on-screen
report editor, you can add or delete text and data character strings which identify
the variable in the computer's Modbus database. [F1] for help describes the
control functions to enable you to format the report easily. Bring up a report
template and move the cursor onto the 'XXXX.XX' fields. Press [Enter] and a
pop-up menu defines the variable being used. Type or edit text anywhere, move
the cursor and keeping pressed [Shift] as you press [$] enables you to enter or
delete any database address from the report.
Utilities
The ‘Utilities’ Menu has several useful tools for setting up and maintaining
OmniCom. The utilities available are:
❑ I/O Point Assignment List ❑ Prover/Batch End Commands
❑ OmniCom Setup ❑ Diagnostics
❑ OmniCom Application ❑ Omni Panel
❑ Archive Maintenance
I/O Point Assignment List

When the configuration of your flow computer is complete, you should review
your assignment of physical I/O by accessing the display under 'I/O Point
Assignment List'. An I/O mismatch can result in erroneous calibration ranges
and consequential errors in measurement and control of your metering system!
This utility shows a summary list that indicates what physical I/O points are
assigned to which variables. Point numbers with asterisks '*' next to them are
used for more than one variable. Check the list to ensure you have not assigned
a physical I/O point to more than one transducer type; e.g.: An I/O point cannot
be assigned to a temperature and pressure transmitter at the same time. The
flow computer will not allow this to happen in the ‘On-line’ mode, but OmniCom
does not check for this in the ‘Off-line’ mode.
OmniCom Setup
This utility allows you to:
❑ Select the type of video monitor.
❑ Turn the sound effects on/off.
❑ Setup the modem command strings.

OmniCom Application
Use this utility before you start to select the software version of OmniCom that
matches the firmware version number of your Omni flow computer. The
firmware versions are:
US VERSIONS METRIC VERSIONS

Turbine / Positive Displacement / Turbine / Positive Displacement /
Coriolis Liquid Flow Metering Coriolis Liquid Flow Metering
20 Systems (with K Factor 24 Systems (with K Factor
Linearization) Linearization)
Orifice / Differential Pressure Liquid Orifice / Differential Pressure Liquid

21 25
Flow Metering Systems Flow Metering Systems
Turbine / Positive Displacement Turbine / Positive Displacement
22 Liquid Flow Metering Systems (with 26 Liquid Flow Metering Systems (with
Meter Factor Linearization) Meter Factor Linearization)
Orifice / Turbine Gas Flow Metering Orifice / Turbine Gas Flow Metering
23 27
Systems Systems
Archive Start/Stop Command

WARNING! When this menu is entered, OmniCom tries to establish communications with
the flow computer using the comm parameter settings currently selected in the
Warning: The flow computer 'Start Comm' submenu of the 'Online' menu. It does this to establish the status
will not accept changes of the 'Archive' flag and 'Archive Config Enable' flag. Check comm settings if all
made to the archive setup
at the time of a 'Transmit items on the menu are inactive; i.e., OmniCom is unable to communicate with
Omni Configuration' upload the target computer.
unless the archiving feature
has been turned off. Any changes made to the flow computers configuration which involves the
format of the data record, number of records in an archive file, or the total
number of archive files within the flow computer, will cause the memory used to
Accessing Help in store the archive data to be reinitialized. This would cause all data stored in
OmniCom - At the 'Using archive to be lost. Therefore, no changes to the target flow computers archive
Help' feature, press [Enter]
and [F1] for editing configuration will be allowed unless automatic data archiving has been disabled
keystrokes. and the 'Archive Config Enable' flag is on.

require further help, call
+1-281-240-6161

Prover Commands
Proving features displayed here can only be viewed when communicating
directly with an Omni Flow Computer.
You may monitor or control the operation of a meter prover which is controlled
by a remote Omni flow computer. You must have already established
communications with the flow computer before making this selection. If you have
not established communications with a flow computer you will receive one of the
following error messages:
Byte count does not match expected - OmniCom is confused and thinks
your modem is connected to a flow computer. Try dialing out first.
No response from Omni - You are either not connected to anything or the
slave ID number of the flow computer you are trying to talk to does not match
OmniCom's setting.
Use the 'Shift' key with the appropriate 'Function' key to select the flowmeter you
wish to remote prove.
The 'Status Window' shows the event history and the 'Omni Display' echoes
data shown locally at the Omni flow computer.
Diagnostics
You must be connected and online with a flow computer for this selection to
work. The screen displays diagnostic information about the flow computer
such as number and type of I/O modules fitted, status of digital I/O, current
output percent of analog outputs and raw input signals coming into the flow
computer.
Omni Front Panel Emulator

When this feature is selected, an illustration of the Omni front panel is displayed
by which all the functions of an Omni Flow computer are emulated. Use the
mouse to click on simulated buttons to access real time displays and make
entries. OmniCom is actually displaying the same LCD display buffer information
and the mouse click are actually sending data into the same key stroke buffer as
the front panel keypad. Performance is much better at 9600 baud or higher. You
must have setup the baud rate and other communication settings in the 'Start
Comm' menu before you can use Omni Panel.
Help
Accessing Help in You can further customize your Help screens by making use of an on-screen
OmniCom - At the 'Using editor. Via this feature you can modify Help text by additions or deletions to suit
Help' feature, press [Enter] your own needs and operations. Windows can be resized and repositioned to
keystrokes. suit your own personal preference. This can be particularly useful as an
additional memory aid, if the Operations Manual is not available to you, or if
additional information is required for other users of this program.

Registration of License and Software Support

For Further Help - If you Remember to mail in the registration of your distribution diskette to Omni flow
require further help, call computers. OmniCom is provided with each Omni flow computer on a single-
user license basis. Any additional installations of this program will require re-
+1-281-240-6161
registration by the user. This will ensure that you will have the opportunity to
receive free telephone support, and notice of program revisions and new add-on
programs for your installation.


Last Updated: 05 06 03 Author(s): K E. TB # 960702
Communicating with Allen-Bradley

Programmable Logic Controllers
Contents
information contained in the Protocol and Error Checking............................................................................. 2
User Manuals, and is
applicable to all firmware PLC Supported.................................................................................................... 2
revisions.
This bulletin was previously Flow Computer Database .................................................................................. 2
published as an appendix to 4th and 5th Digit from the Right Identifies Type of Variable........................................... 2
user manuals of firmware rd
3 Digit from Right Identifies which Area within the Application .................................... 3
revisions Version .70 and
earlier. How the Allen-Bradley Accesses the Omni Flow Computer Database...... 3
PLC-2 ............................................................................................................................ 3
Allen-Bradley PLC-3 ............................................................................................................................ 3
Communications - This PLC-5 ............................................................................................................................ 3
feature allows Valid Starting Addresses of PLC-5 Files ....................................................................... 4
communicating with Allen- 16-Bit Integers............................................................................................................................. 4
Bradley PLCs. However, 8-Character Strings..................................................................................................................... 4
Omni Flow Computers is not 32-Bit Integers............................................................................................................................. 4
responsible for the 32-Bit IEEE Floating Points......................................................................................................... 4
operation, connectivity or Bit Integers.................................................................................................................................. 4
compatibility of Allen- 16-Character Strings................................................................................................................... 4
Bradley products, and 32-Bit Integers............................................................................................................................. 4
furthermore, we do not 32-Bit IEEE Floating Points......................................................................................................... 4
warrant these products.
Scope
All firmware revisions of Omni 6000/Omni 3000 Flow Computers allow
communications with Allen-Bradley Programmable Logic Controllers (PLCs).
This technical bulletin refers to communication aspects specific to the Omni
Flow Computer and serves as information only. Please refer to the manufacturer
for any support or information on Allen-Bradley products.

Abstract
The Omni 6000 flow computer provides serial communications between the flow
computer and an Allen-Bradley Programmable Logic Controller (PLC), usually
via a KE or KF Communication Module connected to the Data Highway. Data is
transmitted serially at a maximum rate of 38.4 kbps using 8 data bits, 1 stop bit
and no parity bit. Average speed of response to a message request is
approximately 75 msec.
Protocol and Error Checking

Both the DFI full duplex protocol and the half duplex protocol are supported.
CRC or BCC error checking can be utilized when using either full duplex or half
duplex.
PLC Supported
The Omni computer supports the following Allen-Bradley PLC types and
messages. Note that bit level operations are not supported.
PLC-2 Unprotected Block Reads and Writes
PLC-3 Word Range Reads and Writes
SLC-502/3 Unprotected Typed Reads and Writes
available at: Flow Computer Database
(281) 240-6161
Email should be sent via Serial Ports #1, #2, #3 and #4 in .71+ firmware revisions support
the WEB Page at: communications using superset of Modbus Protocol. This is the native
www.omniflow.com communications language of the flow computer. Several thousand variables are
or email to: available within the Database. The primary numbering system used to identify
techsupport@omniflow.com these variables is their 'index number'. The actual digits of the index number
indicate the type of variable and in many cases application area within the
computer.
4th and 5th Digit from the Right Identifies Type of

Variable
1??? Variable is a digital status or command bit
3??? Variable is a 16 bit signed integer
4??? Variable is a 8 character ASCII string
7??? Variable is a 32 bit IEEE floating point
14??? Variable is a 16 character ASCII string

TB-960702 Communicating with Allen-Bradley Programmable Logic Controllers
3rd Digit from Right Identifies which Area within the

Application
?1?? Variable relates to Meter Run #1
?5?? Variable is scratchpad
?6?? Variable is PID related or scratchpad
?7?? Variable is a command write.
?8?? Variable is related to station functions
?9?? Variable is related to prover functions
How the Allen-Bradley Accesses the Omni

Flow Computer Database
PLC-2
This family is usually limited as to the type of data and address range. Data is
always transferred as block reads and writes.
Five translation tables are provided where the user can specify what data within
the database will be concatenated into read or write groups. The starting
address of each data block is selectable.
Note: The PLC2 does not ❏ Translation Tables #1 through #3 are used to set up block reads which
understand 32-bit integer or can contain status points packed 16 to a word, 16-bit or 32-bit integers
32-bit IEEE floating points
but can pass these variable and IEEE floating points.
types to devices that do ❏ Translation Table #4 is used for block writes of status and command bits
understand them.
only. Data is packed 16 to a word.
❏ Translation Table #5 provides for block writes to any selected data.
PLC-3
This family can use the methods described above as well as 'word range reads
and writes' of any variable within the database (see PLC-5 list for starting
addresses).
PLC-5
This family utilizes 'typed reads and writes' of the complete Database. To
accommodate the PLC-5 'file system’ method of addressing, the Modbus index
numbers serve as the basis of the internal file system of the computers as it
appears to a PLC-5 device. Table below shows typical examples:

MODBUS INDICES VERSUS PLC-5 ADDRESSES

MODBUS INDEX # PLC-5 ADDRESS ELEMENT SIZE COMMENT
1101 N11:01 1 Word (16 Flags) Meter #1 Status Flags
1217 N12:17 1 Word (16 Flags) Meter #2 Status Flags
1701 N17:01 1 Word (16 Flags) Command Flags
3201 N32:01 1 Word (Integer) Meter #1 Data
3210 N32:10 1 Word (Integer) Offsets track
3901 N39:01 1 Word (integer) Prover Data
4101 B41:01 1 Byte (ASCII) 4 Words per Variable
4102 B41:02 1 Byte (ASCII) 1 Byte per element
5101 N51:01 1 Word (Long Integer) 2 Words per variable
5102 N51:02 1 Word (Long Integer) 2 Words per variable
5103 N51:03 1 Word (Long Integer) Same again
7401 F74:01 2 Words (IEEE Float) 2 Words per variable
7405 F74:05 2 Words (IEEE Float) Offsets track
Valid Starting Addresses of PLC-5 Files
16-Bit Integers
N10:01 N11:01 N12:01 N13:01 N14:01 N15:01 N16:01 N17:01 N18:01 N19:01
N30:01 N31:01 N32:01 N33:01 N34:01 N35:01 N36:01 N37:01 N38:01 N39:01
8-Character Strings
B41:01 B42:01 B43:01 B44:01 B45:01 B46:01 B47:01 B48:01 B49:01
32-Bit Integers
N51:01 N52:01 N53:01 N54:01 N55:01 N58:01 N59:01
32-Bit IEEE Floating Points

F70:01 F71:01 F72:01 F73:01 F74:01 F75:01 F76:01 F77:01 F78:01 F79:01
Bit Integers
N130:01 N134:01
16-Character Strings
B140:01
32-Bit Integers
N150:01
32-Bit IEEE Floating Points

F170:01

Date: 05 09 03 Author(s): K. E. TB # 960703
Storing Archive Data within the Flow

Computer
Contents
information contained in Raw Data Archiving ............................................................................................ 2
Volume 2 and Volume 3,
and is applicable to all Retrieving Data.............................................................................................................. 3
firmware revisions 71+. Raw Data Archive Point Addresses............................................................................... 4
This bulletin was previously Retrieving Text Archive Data Including Alarm and Audit Trail Logs Using OmniCom ... 5
published as an appendix to Retrieving Text Archive Data Using OmniCom........................................................................... 5
user manuals of firmware Reading the Historical Audit trail from an Omni using OmniCom: ............................................... 6
revisions Version .70 and Reading the Historical Alarm Log using OmniCom:.................................................................... 6
earlier.
Archive Configuration Changes..................................................................................... 7
Setting the 'Reconfig Archive' Flag ............................................................................................. 8
Possible Loss of Data when Starting and Stopping the Archive ................................................. 8
Data Archiving - The
Defining the Archive Records ..................................................................................................... 8
archiving feature allows you
to store raw data, ASCII text How The Available Memory Is Allocated ....................................................................... 9
data and historical reports. Checking The Archive File Memory Status Screens ................................................... 10
Summary 0f Raw Data Archiving Features.................................................................. 11
Raw Data Archive Definition: Alarm/Event Log and Audit Event Log ........ 12
Alarm/Event Log Record Structure: Archive File Address 711 .................................... 12
Audit Event Log Record Structure: Archive File Address 712. .................................... 12
Using The Custom Reports to Access the Text Archive Feature................ 13
Custom Report Templates ............................................................................... 14
Scope
All firmware revisions of Omni 6000/Omni 3000 Flow Computers have the
archiving feature. This feature allows you to archive raw data, ASCII data and
historical reports.

Abstract
Definitions & Terminology The flow computer provides three distinct methods of storing data. These are as
follows:
Archive Address - A
unique Modbus address
used to read a data record 1) Raw Data Archive Data records are defined and stored in raw binary
from an archive file. These format in circular files of 'n' records per file. Ten user
addresses are in the 700 configurable files are provided as well as an alarm
series; i.e., 701, 702, 703,
etc. file and audit trail file. This data can be retrieved
using standard Modbus Function Codes 3 and 6.
Archive Record - A
structure containing a fixed 2) Text Archive Data ASCII data which is captured and saved whenever a
set of data variables, which
cannot exceed 250 bytes in
Snapshot, Daily, Batch End or Prove report is
length. Data within the printed. Data is stored chronologically. To retrieve
record can be of any valid this data you must use OmniCom, OmniView or
data type in any order. a custom Modbus driver that understands the
Archive Trigger Boolean - proprietary Omni Modbus Function Codes 64 and
The actual event, which
causes the flow computer to 65.
capture and store a record
within the archive file. The 3) Historical Reports These are exact copies of data that was sent to the
trigger can be any Boolean local printer in ASCII format. The flow computer
variable within the database stores the last eight copies of each of the following
including the result of a reports: Daily, Batch End and Prove.
Boolean statement.
Block Read - Modbus
protocol block read requires Method 3 is limited to storing the last eight reports and is therefore not
that Function Code 03 (read considered archive data. Therefore this chapter will be limited to describing how
multiple registers) be used
Methods 1 and 2 are used to store archive data within the flow computer.
to retrieve data.
Circular Archive File - A
file of ‘n’ records arranged
as a circular buffer which
always contains the most
Raw Data Archiving
recent ‘n’ records; i.e., the A maximum of ten archive files can be user configured. Two additional archive
oldest data record is
overwritten by each new files, the alarm archive and audit trail archive are also included but are fixed in
record as it is added. format and cannot be user configured.
Current Record Pointer - A
16-bit read-only integer Each user configurable archive file consists of 'n' archive records, where 'n' is
register containing a defined by the user. A record consists of a time and date stamp followed by a
number between 0 and ‘n’, number of user-defined variables of any valid data type as described by its
representing the position of
archive record definition table. The amount of memory an archive consumes is
the most recently added
record within the archive calculated by multiplying the record size in bytes times the number of records in
file. The pointer is adjusted the archive. Associated with each archive file is an archive trigger Boolean.
after each complete record Data is captured and stored in each of the archive files whenever the
is added. A value of 0
indicates that no data
appropriate trigger occurs; e.g., at the end of a batch or beginning of the day,
records have been added etc. Three additional registers per archive file serve to indicate (a) maximum
since the last initialization of number of records, (b) current record pointer and (c) requested record to read
the archive memory. pointer.
(Continues…)

TB-960703 Storing Archive Data within the Flow Computer
Retrieving Data
Definitions & Terminology Data records are retrieved one record at a time by writing the number of the
record required, to the requested record pointer register. The data can then
(…Continued) be accessed immediately by a block read of the archive address. Data must
be read as one complete block. Also, because the flow computer always
Maximum Records responds with a complete record, the 'number of registers' field of the Modbus
Register - A 16-bit read- poll request is ignored by the flow computer.
only integer adjacent to the
‘Current Record Pointer’ The following record retrieval method is simple and efficient; it works well
which contains the number
‘n’, indicating the maximum
assuming that there is only one host device retrieving data. The method
number of records within the assumes that the number of the last record retrieved is left in the requested
archive file. record pointer within the flow computer. This will not be the case when more
Requested Record than one host device will be retrieving data; in this case each host device must
Pointer - A 16-bit read/write know the number of the last record it retrieved.
integer used to select a
specific record within an 1) Read the maximum records register, current record pointer and
archive file.
requested record pointer. These registers are adjacent to each other in
Time and Date Stamp - Six
bytes of binary data the flow computers database.
representing the date and 2) A current record pointer value of 0 indicates that the archive file has
time that the archive record been initialized (i.e. cleared to binary zeroes/ASCII Nulls) and no trigger
was stored. The byte order
is as follows: event has occurred since initialization).
❑ Byte 1 = Month (1-12) or 3) Compare the contents (just read) of the current record pointer with the
Day (1-31) requested record pointer.
❑ Byte 2 = Day (1-31) or
Month (1-12)
4) If the records numbers are equal no additional records have been added
since the last read and no further action is needed.
❑ Byte 3 = Year (0-99)
❑ Byte 4 = Hour of Day (0- 5) If the record numbers are not equal, increment the value of requested
23) record pointer.
❑ Byte 5 = Minute (0-59) 6) If the resultant value is greater than the value obtained from the
❑ Byte 6 = Seconds (0-59) maximum record pointer, roll-over has occurred and record number one
❑ European Format should be retrieved by writing '1' to the requested record pointer
Selected (dd/mm/yy) register. Otherwise write the incremented value to the requested record
Valid Data Types - pointer register.
❑ 32-bit IEEE floating point
data
7) After writing to the requested record pointer register in the flow
computer, the selected archive record can be read immediately using
❑ 32-bit long integer data
Modbus function '3' (read multiple registers). Archive file addresses are in
❑ 16-bit integer data
the 700 area of the flow computers database (i.e., archive file 1 = 701,
❑ 8-byte ASCII string data;
byte packed Boolean
archive file 2 = 702 etc.).
status data 8) Repeat steps 3 through 7 until all records are read.
During the normal course of events, the host attempts to read the next record in
sequence based on the number of the last record it retrieved. An archive record
containing binary 0s indicates that the archive has been initialized since the last
read and that the host should restart by reading record number one (assuming
that the current record pointer is not 0).

Raw Data Archive Point Addresses
Archive #1 Record Access Address Read Only 0701

Access Record Date/Time Only Read Only 0751
Maximum # of Records Read Only 3701
Last Record Updated Pointer Read Only 3702
Record Req To Read Pointer Read/Write 3703


Getting Tech Support - Maximum # of Records Read Only 3728
Technical support is Last Record Updated Pointer Read Only 3729
available at: Record Req To Read Pointer4 Read/Write 3730
(281) 240-6161
Alarm Archive Record Access Address Read Only 0711
Email should be sent via
the WEB Page at: Access Record Date/Time Only Read Only 0761
www.omniflow.com Maximum # of Records Read Only 3731
or email to:
techsupport@omniflow.com
Audit Archive Record Access Address Read Only 0712
Retrieving Text Archive Data Including Alarm and Audit

Trail Logs Using OmniCom
Retrieving Text Archive Data Using OmniCom
For use with Omni Revisions 2x.70 and below:

Step 1. OmniCom writes ‘archive data start’ to Modbus index 15128 using
YY/DD/MM format.
NOTE - In revision 2x.71
and above, Omni converts Step 2. OmniCom writes ‘number of days’ archive to retrieve’ to Modbus
packet number to 0 to 63
even if OmniCom asks for index 15127.
64 and above.
Step 3. OmniCom reads 15127
In revision 2x.70 and below, If 15127 = minus number go to step 4
Omni expects the packet If not go to step 3
number within 0 – 63.
Step 4. OmniCom sets packet number = 0
Step 5. OmniCom reads Modbus index 9402 with the current packet
number
using functions code 65.
If ‘1A’ is received, go to step 7,
but if you receive packet number = packet +1,
packet number >=64 go to step 6,
If you receive anything else go to step 5.
Step 6. OmniCom reads 15127, if 15127 = positive number, write this
number to 15127, go to step 3
archive retrieving.
For use with Omni Revisions 2x.71 and above:

Step 1. OmniCom writes ‘archive data start’ to Modbus index 15128 using
YY/DD/MM format.
Step 2. OmniCom writes ‘number of days required’ to Modbus index 15127
Step 3. OmniCom reads 15127
If 15127 = minus number go to step 4

If not go to step 3
Step 4. OmniCom sets packet number = 0
Step 5. OmniCom reads Modbus index 9402 with the current packet
number using function code 65.
If ‘1A’ is received, go to step 7,
If not packet number = packet number + 1.
Step 6. OmniCom reads 15127,
If 15127 = positive number, write this number to 15127 go to step 3,
If not go to step 5.
Step 7. OmniCom writes a 999 to Modbus index 15127 to terminate text
archive retrieving.
Reading the Historical Audit trail from an Omni using OmniCom:

Step 1. OmniCom writes the number of audit events to be retrieved to
Modbus register 3769 (Minimum 1, maximum 150). The Omni will
send the maximum number of events available in cases where the
number asked for exceeds the number available.
Step 2. OmniCom writes the appropriate bit to Modbus index 15129
command word to initiate the transfer process.
Step 3. OmniCom continually reads 15129 until the target bit is et to zero by
the Omni indicating that the command is recognized and the buffer
is filled.
Step 4. OmniCom initializes the packet number to zero.
Step 5. Using function code 65, OmniCom reads the 9042 text buffer using
the current packet number. If the retrieved text contains “EOF” (1A
hex), go to step 6. If the packet number = packet number +1. There
is no need to limit the packet number to 64. Repeat step 5.
Step 6. The audit trail retrieval process is complete.
Reading the Historical Alarm Log using OmniCom:
Step 1. OmniCom writes the number of historical alarm events to be

retrieved to Modbus register 3769 (minimum 1, maximum 500**).
The Omni will send the maximum number of events available in
NOTE – Firmware revisions
cases where the number asked exceeds the number available.
2x.71 and above store a
maximum of 500 alarm Step 2. OmniCom writes a ‘1’ to the appropriate bit in the 15129 command
events.
word to initiate the transfer process.
Firmware revisions 2x.70
and below store 150 alarm Step 3. OmniCom continually reads 15129 until the target bit is set to zero
events. by the Omni indicating that the command is recognized and the
buffer is filled.
Step 4. Omnicom initializes the packet number to zero.
Step 5. Using function code 65, OmniCom reads the 9042 text buffer using
the current packet number. If no response is obtained, a 64-packet

boundary has been reached and the Omni is refilling the buffer (3
second maximum delay). The buffer read should be retried. If the
retrieved text contains ‘EOF’ (1A hex), go to step 6. If the retrieved
text contains packet number = packet number + 1. There is no
need
to limit the packet number to 64. Repeat step 5
Step 6. The alarm retrieval process is complete.
Archive Configuration Changes

Archive configuration changes can be made via OmniCom or directly from the
keypad of the flow computer. As the OmniCom program includes extensive help
screens, which document this subject, this appendix will concentrate on
configuring the archive features via the keypad.
From the Display Mode press [Prog] [Setup] [Enter]. The LCD screen displays:
*** SETUP MENU ***

Misc Configuration _
Time/Date Setup
Station Setup
Select 'Misc. Configuration' and press [Enter]. The following displays:
*** MISC SETUP ***

Password Maint?(Y) _
Check Modules ?(Y)
Config Station?(Y)
Select 'Password Maint' and press [Enter]. Enter the privileged password
when prompted and scroll down the screen until the following is displayed:
PASSWORD MAINTENANCE
Reconfig Archive ? Y
Archive Run?(Y/N) N
Reset All Totals ?

Setting the 'Reconfig Archive' Flag

Any configuration changes that are made to any of the archive files such as
changes to the size or number of records will force the flow computer to
reallocate and clear to zero the RAM memory used to store archive data. To
avoid accidental data loss, the flow computer requires that two entries are
manipulated correctly before changes to the archive configuration can be made.
The 'Reconfig Archive' flag must be set to 'Y’ and the Archive Run' flag must
be set to 'N'.
Possible Loss of Data when Starting and Stopping the Archive

To conserve archive storage, the user may on some occasions wish to set the
'Archive Run' flag to ‘N’. This can be done at any time without loss of existing
data as long as the 'Reconfig Archive' flag is not set to 'Y'. If the 'Reconfig
Archive' flag is accidentally set to 'Y' no data will be lost until the 'Archive Run'
flag is set to 'Y' (this allows the user to retrieve data before it is lost).
Defining the Archive Records

After setting the 'Reconfig Archive' flag to 'Y' as described above, press the
[Prog] key once to return to the 'Misc Setup' menu. It will be possible to define
or change any archive file configuration by scrolling down the display until the
following screen is displayed:
*** MISC SETUP ***

Archive File "n" _
Enter a number between 1 and 10 to select a specific archive file to modify (1 for
example). The following screen will display:
ARCHIVE 701 RECORD

#1 Index 0
#1 Points 0
#2 Index 0
#2 Points 0
Begin entering the data that you require to be archived. The example below will
cause variables 7101, 7102, 7103, 5101, 5102 and 5103 to be archived.
INFO - The ‘Alarm’ and
‘Audit Trail’ archive files are ARCHIVE 701 RECORD
fixed format and cannot be #1 Index 7101
changed.
#1 Points 3
#2 Index 5101
#2 Points 3

A maximum of 16 groups of variables may be included in an archive record.

Data can be of any valid type. The record is limited to a total of 250 data bytes
remembering that the time and date stamp included in each record occupies 6
bytes. Scrolling down the screen displays the following:
ARCHIVE 701 RECORD

Max Records 0
Trig Boolean 0
Circular Archive File - A Enter the maximum number of archive records to be contained within this
file of ‘n’ records arranged circular archive file.
as a circular buffer which
always contains the most At the 'Trig Boolean' entry, enter the database address of the Boolean trigger,
recent ‘n’ records; i.e., the
oldest data record is
which will cause the flow computer to store the archive data record. For
overwritten by each new example, entering 1831 (the 'hour start’ flag) would cause the flow computer to
record as it is added. store data at hourly intervals.
Once you have entered all the necessary data for all of the archive records
return to the following screen, which is in the 'Password Maintenance' menu.
Reconfig Archive ? Y
Archive Run (Y/N) N
INFO - Redefining the Set 'Reconfig Archive' to 'N' and 'Archive Run' to 'Y'. At this point the flow
archive Boolean trigger computer will reinitialize archive RAM memory and attempt to allocate memory
does not cause the archive
RAM to be cleared.
as configured.
How The Available Memory Is Allocated

Approximately 250,000 bytes of memory are available for the storage of
archived data; this includes 'Raw Data' and 'ASCII Text Data'. Archive memory
is allocated dynamically, i.e. the memory required to satisfy the 'Raw Data
Archive' is allocated first, one archive file at a time. The memory remaining after
the Raw Data Archive files are setup is what is used by the Text Archive
described later.

Checking The Archive File Memory Status Screens

The 'Archive File Memory Status' screens display automatically whenever the
user attempts to re-start data archiving for the first time after reconfiguring the
archive structure. These screens can also be accessed at any time by pressing
'Setup' 'Status' 'Display' while in the display mode. A correctly configured
archive structure is indicated by the following screen.
INFO - The number of files
allocated changes ARCHIVE FILE STATUS
depending on how many Archive Memory OK
archive files have been
configured
Files Allocated 3
An incorrectly configured archive structure is indicated by the following screen.
ARCHIVE FILE STATUS

Archive Memory Error
Files Allocated 3
Archive memory errors are caused when RAM memory is insufficient for the
number and size of archive files configured. In this case the 'Start Archive'
command is ignored and the flow computer allocates memory to as many
archive files as possible. The number on the 'Files Allocated' line of the display
shows how many files were allocated before the memory ran out.
Scroll down the screen to see the actual number of bytes allocated to each
archive file. All remaining memory not allocated to the 'Raw Data Archive Files'
is allocated to the 'Text Archive' buffer. The display below is typical.
ARCHIVE FILE STATUS

709 ArcSize 10000
710 ArcSize 8192
TextArcSize 100256

Summary 0f Raw Data Archiving Features

❏ Ten independent archive files are available for user configuration.
❏ Two additional archive files, the 'alarm event log' and 'audit trail log' are
provided.
❏ Archive files consist of multiple records in a circular array.
❏ Mixed types of variable data can be stored in records of 250 bytes
maximum.
❏ Except for the 'alarm log' and 'audit trail log', content and maximum
number of records in an archive file are configurable.
❏ Data is read in block form one record at a time.
❏ Each archive has a unique address (701, 702, 703, etc.).
❏ Each archive has a set of integer registers used to indicate most current
record pointer, maximum number of records, and required record pointer.
❏ Data is captured and stored in an archive file whenever the appropriate
trigger event occurs.
❏ Multiple archive files can be controlled by the same trigger event.
❏ Empty archive records contain binary 0’s / ASCII Null characters.
❏ To avoid errors, host devices reading archive data should dynamically
determine the record pointer roll over value based on the number of
record integers read each time from the flow computer.
❏ Any configuration changes made to the archive setup such as redefinition
of any record or change in the number of records within any archive will
cause all data stored in the entire archive system to be reset. To prevent
accidental erasure of all archived data the user must first halt all archiving
by setting the ‘Archive Run/Halt Flag' to false (0), and setting the 'Config
Archive Flag' to true (1).

Raw Data Archive Definition: Alarm/Event Log

and Audit Event Log
Alarm/Event Log Record Structure: Archive File Address

711
Note: Alarm types are:
0 = Log event, sound Field #1 3-Byte Date (MM, DD, YY or DD, MM, YY)
beeper and display in
LCD any edge change Field #2 3-Byte Time (HH, MM, SS)
in bit identified by field
#3.
Field #3 16-Bit Integer (Modbus Index # of alarm or event)
1 = Log event, sound Field #4 1 Byte (Alarm Type - see sidebar)
beeper and display in
LCD rising edge Field #5 1 Byte (Boolean Value, 1 or 0 representing Alarm or OK)
changes in bit identified
by field #3 Field #6 IEEE Float (Value of transducer variable at the time of alarm
2 = Event log any edge or event)
change in bit identified
by field #3. No beeper Field #7 32-Bit Integer (Volume totalizer at time of event or alarm)
or LCD display action.
3 = Event log rising edge Field #8 32-Bit Integer (Mass totalizer at the time of the event or alarm)
changes in bit identified
by field #3. No beeper
or LCD display action.
Rising edge change means
Audit Event Log Record Structure: Archive File Address
0 to1 transition. 712.
Field #1 3-Byte Date (MM, DD, YY or DD, MM, YY)

Field #2 3-Byte Time (HH, MM, SS)
Field #3 16-Bit Integer (Event number, increments for each event, rolls
at 65535)
Field #4 16-Bit Integer (Modbus index of variable changed)
Note: Fields 5 and 6 are set Field #5 IEEE Float (Numeric variable value before change - old
to 0.0 when the variable value)
type changed is String.
Fields 7 and 8 contain null Field #6 IEEE Float (Numeric variable value after change - new
characters when the value)
variable type changed is
NOT a string. When fields 7 Field #7 16-Char ASCII (String variable value before change - old value)
and 8 contain 8 character
strings the remaining 8 Field #8 16-Char ASCII (String variable value after change - new value)
characters are padded with
nulls. Field #9 32-Bit Integer (Volume totalizer at time of change)
Field #10 32-Bit Integer (Mass totalizer at the time of the change)

Using The Custom Reports to Access the Text

Archive Feature
The actual data which will be archived in the 'Text Archive' buffer is identified
within the body of a 'User Custom Report Template'. This is done by enclosing
the data in question between braces '{}' and preceding the opening brace '{'
character with either Boolean 1000 (archive the data identified between the
braces) or Boolean 2000 (print and archive the data identified between the
braces). In the example 'Batch End' report shown below, the first half of the
report will be printed and stored in the 'Text Archive' while the second half of the
report will not print but will be stored in the 'Text Archive'.
X{ Company Name
The user has embedded a Batch Report
Boolean point address 2000
to indicate that the following Date : XX/XX/XX Time : XX:XX:XX Computer ID : XXXXXXX
data enclosed by the ‘{…}’
characters is to be printed Meter ID XXXXXXXX XXXXXXXX XXXXXXXX
and archived. Product ID XXXXXXXX XXXXXXXX
API Table Selected XXXXXXXX XXXXXXXX
When embedding the point, Batch Start Date XX/XX/XX XX/XX/XX
set the width=1 Batch Start Time XX:XX:XX XX:XX:XX
and number of decimal Batch End Date XX/XX/XX XX/XX/XX
places=0. Batch End Time XX:XX:XX XX:XX:XX
Batch Gross (IV) BBL XXXXXXXXX XXXXXXXXX XXXXXXXXX
Batch Net (GSV) BBL XXXXXXXXX XXXXXXXXX XXXXXXXXX
Batch Mass LB XXXXXXXXX XXXXXXXXX XXXXXXXXX}
X{
Opening Gross (IV) BBL XXXXXXXXX XXXXXXXXX XXXXXXXXX
The User has embedded a Opening Net (GSV) BBL XXXXXXXXX XXXXXXXXX XXXXXXXXX
Boolean point address 1000 Opening Mass LB XXXXXXXXX XXXXXXXXX XXXXXXXXX
to indicate that the following Closing Gross (IV) BBL XXXXXXXXX XXXXXXXXX XXXXXXXXX
data enclosed by the ‘{…}’ Closing Net (GSV) BBL XXXXXXXXX XXXXXXXXX XXXXXXXXX
Closing Mass LB XXXXXXXXX XXXXXXXXX XXXXXXXXX
characters is to be archived
Batch Flow Weighted Averages:
only and not printed. Gross Flow (IV) BBL/HR XXXXXX.X XXXXX.X
When embedding the point, Temperature Deg.F XXXXXX.X XXXXX.X
set the width=1 Pressure PSIG XXXXXX.X XXXXX.X
and number of decimal Flowing Density GM/CC XXXXXX.X XXXXX.X
places=0. API @ 60 Deg.F XXXXXX.X XXXXX.X
VCF X.XXXX X.XXXX
CPL X.XXXX X.XXXX
Meter Factor X.XXXX X.XXXX
}
INFO - Data is archived only The template files shown below can be used to archive text data whenever the
when the report is report is processed.
processed for the first time.
Reprinting a stored report 1) 'FILENAME.TP1' Snapshot Report
does not cause any data to
be stored in the archive. 2) 'FILENAME.TP2' Batch Report
3) 'FILENAME.TP3' Daily Report
4) 'FILENAME.TP4' Prover Report

Custom Report Templates

A default selection of files with the extension 'TP?' are created automatically
when OmniCom is installed, They can be found in the 'OMNI2?' subdirectories.
For example the OMNI20 subdirectory contains the following template files:
REV20A.TP1 Interval Report Independent Products

REV20A.TP2 Batch Report Independent Products
REV20A.TP3 Daily Report Independent Products
REV20A.TP4 Prove Report Independent Products Double Chronometry
REV20B.TP1 Interval Report Independent Products
REV20B.TP2 Batch Report Independent Products
REV20B.TP3 Daily Report Independent Products
REV20B.TP4 Prove Report Independent Products Normal Pipe Prover
REV20C.TP1 Interval Report Common Product
REV20C.TP2 Batch Report Common Product
REV20C.TP3 Daily Report Common Product
REV20C.TP4 Prove Report Common Product Double Chronometry
REV20D.TP1 Interval Report Common Product
REV20D.TP2 Batch Report Common Product
REV20D.TP3 Daily Report Common Product
REV20D.TP4 Prove Report Common Product Normal Pipe Prover
REV20E.TP4* Prove Report Master Meter Method
REV20M.TP4* Prove Report Mass Meter Proving Normal Pipe Prover
REV20MC.TP4* Prove Report Mass Meter Proving Double Chronometry
REV20LC.TP4* Prove Report Double Chronometry Viscosity Linearization
REV20LP.TP4* Prove Report Pipe Prover Viscosity Linearization
Note: Templates can only be accessed if they exist; i.e., if you are currently working
* To avoid duplication and on 'FILENAME.OMI' opening the custom templates will just create an empty file.
conserve disk space You must first create a set of templates by copying the appropriate sample
these templates do not templates as follows:
have matching TP1,
TP2 and TP3 templates.
Select TP1 though TP3
1) At the OmniCom File menu select 'Shell to DOS'.
from the appropriate set
2) Type the following to create a set of custom templates for a common
(A, B, C or D) above
depending on product system using a full sized pipe prover (assumes Rev. 20.xx
independent or common application):
product.
COPY OMNI20\REV20D.TP? OMNI20\filename.TP?
3) Type EXIT to return to OmniCom.
In the above example OMNI20 is the sub directory which contains all files
related to Application Revision 20. Likewise OMNI24 refers to Revision 24
applications.

Date: 05 13 03 Author(s): K.E. TB # 960704
Communicating with Honeywell

ST3000/STT3000 Smart Transmitters
Contents
information contained in the Digitally Enhanced (DE) Protocol Overview .................................................... 2
User Manual, and is
applicable to all firmware Transmitter Database ......................................................................................... 2
revisions.
This bulletin was previously
Using the Honeywell Handheld Communicator............................................ 3
published as an appendix to Combo Module LED Status Indicators ............................................................. 3
user manuals of firmware
revisions Version .70 and Switching Between Analog and Digital Mode.................................................. 4
earlier. Auto Mode..................................................................................................................... 4
Manual Operation.......................................................................................................... 4
Communication with Viewing the Status of the Honeywell Transmitter from the Omni Front
Honeywell Panel .................................................................................................................... 4
ST3000/STT3000 Smart
Transmitters - This feature
allows you to communicate
with Honeywell Smart
Temperature and Pressure
Transmitters, via Omni’s H
type Process I/O Combo
Module and using
Scope
Honeywell’s DE Protocol.
All firmware revisions of Omni 6000/Omni 3000 Flow Computers have the
feature of communicating with Honeywell ST3000 Smart Transmitters. This
feature uses Honeywell’s Digitally Enhanced (DE) Protocol and requires that an
H Combo I/O Module be installed in your flow computer.
Abstract
Using 'H' Combo I/O Modules, the Omni Flow Computer can communicate with
Honeywell Smart Temperature and Pressure Transmitters using Honeywell’s
DE Protocol. Up to 4 transmitters can be connected to each 'H' Type Combo
Module, with loop power being provided by the combo module.

Digitally Enhanced (DE) Protocol Overview

Getting Tech Support - Digital data is transmitted serially between the flow computer and Honeywell
Technical support is Smart Transmitters by modulating the current in the two wire loop connecting
available at:
the devices. Power for the transmitter is also taken from this current loop. Data
(281) 240-6161
is transmitted at 218.47 bits per second with a digital '0' = 20 mA and a digital '1’
Email should be sent via = 4 mA.
the WEB Page at:
www.omniflow.com In normal operation, the Honeywell transmitter operates in the '6-byte Broadcast
or email to: Mode'. In this mode, the transmitter transmits the following data to the flow
techsupport@omniflow.com computer every 366 msec:
Byte #1 Status Flags
Byte #2-#4 Process Variables % Span Value (3-byte floating point)
Byte #5 Database ID (indicates where in the transmitters database Byte
#6 below belongs)
Byte #6 Database Data Value
Transmitter Database
By using the data contained in Bytes #5 and #6, the flow computer builds and
maintains an exact copy of the smart transmitters configuration database. A
transmitter database varies in size from about 90 bytes for a pressure
transmitter to 120 bytes for a temperature transmitter. It takes between 30 and
45 seconds to completely build a copy of the transmitter database within the
flow computer. The transmitter database is continuously compared against the
flow computer configuration settings for that transmitter. The flow computer
automatically corrects any differences between the databases by writing the
correct configuration data to the transmitter.

TB-960704 Communicating with Honeywell ST3000 Smart Transmitters
Using the Honeywell Handheld

Communicator
The flow computer is responsible for configuring the following entries within the
transmitter:
1) Lower Range Value (LRV) or Zero
2) Transmitter Span or Upper Range Limit (URL)
3) Damping Factor
4) Tag Name
Any changes made to 1, 2 and 3 using the handheld communicator will be
overwritten by the flow computer. In the digital mode it is not necessary to
calibrate the transmitter output using the handheld communicator. The digital
signal can be calibrated using the normal Omni analog input method described
in Chapter 8 of Volume 1.
Combo Module LED Status Indicators

Each I/O channel of the 'H' Combo module has a set of two LED indicators, one
green and one red. The green LED shows all communication activity taking
place on the channel (flow computer, transmitter and handheld communicator if
connected). The Red LED lights only when the flow computer is transmitting
data to the transmitter.
Normal digital operation is indicated by a regular pulsation of the green LED
(about 3 per second). The red LED will be seen to blink whenever a
configuration change is made in the flow computer which affects that particular
transmitter.

Switching Between Analog and Digital Mode.
Auto Mode
Connecting an analog mode Honeywell smart transmitter to the computer will
cause the flow computer to automatically switch the transmitter to the digital DE
mode, sending out a communication request to the Honeywell transmitter. A
switch over to the digital mode by the transmitter will cause the green LED on
the H combo module to pulse steadily indicating that communications have been
established.
Manual Operation
For manual operation, do the following:
1. Disable communications between the Honeywell transmitter and the flow
computer by deleting all I/O point assignments within the flow computer to
that I/O point.
2. Using the Honeywell SFC, SCT or any Honeywell handheld
communicator, press [Shift] [A/D] and wait till the handheld displays
'Change to Analog?'
3. Answer (Yes) by pressing [Enter]. ‘SFC Working’ will be displayed. The
'H' Combo module’s green LED on that channel will stop pulsing.
4. Re-enter the I/O point to cause the Omni to send the communication
request command to the Honeywell and after three command sends the
green LED on the Honeywell module will pulse at a steady 3Hz rate.
Viewing the Status of the Honeywell

Transmitter from the Omni Front Panel
To verify the data being received from the smart transmitter, press [Input],
[Status] and [Enter] from the front panel. The following displays:
H1-2 Transmitter
PV% - 25.00
Status IDLE
LRV .0
SPAN 150.0
Damp Sec. .00
Conformity bit 0
SW Revision 2.1
Serial # xxxxxxxx
Transmitter Type GP
URL 3000
ID/TAG PT202
SV .00

H1-2 Transmitter : Indicates the Honeywell Combo Module (H1) and the
channel number on that module (Channel 2 in this case).
PV% : Process variable value in percentage of the transmitter’s

span. A -25.00 displayed on the Omni could mean that
the transmitter is not communicating (see Status
definition below).
Status : There are five status states.
1) OK : Communications between the flow

computer and smart Honeywell transmitter
are OK. The database within the
transmitter matches the flow computer.
2) Idle : This flow computer I/O point has been

assigned to a Honeywell transmitter but is
not receiving data from the transmitter.
Possible cause is a wiring problem such
as reversal of wiring. If you observe the
status LEDs you will note that the flow
computer attempts to establish
communications by sending a wake-up
command every 10 seconds or so.
3) Bad PV : Communications between the flow

are OK but the transmitter has determined
that a critical error has occurred within the
transmitter meaning the value of the
process variable cannot be trusted. The
flow computer will set the transducer
failure alarm and follow the fail code
strategy selected by the user for this
transducer.
4) DB Error : Communications between the flow

are OK but the flow Computer has
determined that the database within the
flow computer does not agree with the
database within the transmitter. If you
observe the status LEDs you will note that
the flow computer attempts to correct the
transmitters database by writing the
correct data to the transmitter once every
30-45 seconds or so.

5) 4 Byte : The transmitter is operating in the 4-Byte

Broadcast Mode. Because the flow
computer will not tolerate this mode of
operation, this status display should only
be displayed momentarily as the flow
computer will automatically switch the
transmitter into the 6-Byte Broadcast
Mode.
LRV : Lower Range Value of the transmitter in engineering

units. Engineering units are degrees Celsius for
temperature transmitters, inches of water for differential
pressure transmitters, and pounds per square inch for
pressure transmitters.
Span : The Span of the transmitter in engineering units (the

Span is the difference between the lower and upper
ranges of the transmitter). Engineering units are degrees
Celsius for temperature transmitters, inches of water for
differential pressure transmitters, and pounds per square
inch for pressure transmitters. The flow computer will
display ‘DB Error’ if the user tries to enter a span of 0% or
a span which would exceed the transmitter’s upper range
limit' (URL).
Damp Seconds : Damping Time of the transmitter output in seconds.
Conformity Bit : Meaningful only with differential pressure transmitters.

Conformity Bit 0 = linear output; Conformity Bit 1 =
square root output. This bit should always be 0 for smart
temperature transmitters.
Software Revision : Current Software installed within the smart device.
Serial # : Serial Number of the smart transmitter.
Transmitter Type : Valid transmitter types are:
TT = Temperature Transmitter
DP = Differential Pressure Transmitter
GP = Gauge Pressure Transmitter

URL : Upper Range Limit of the transmitter in engineering units.

The transmitter will not accept configuration entries which
exceed this value.
ID/TAG : ASCII string used to identify the transmitter.
SV : Secondary Process Variable Value expressed in °C. This

represents sensor temperature for pressure transmitters,
and junction temperature for temperature transmitters.
The flow computer may or may not have a value in this
field, depending upon whether the SV is included in the
part of the transmitter’s database which is sent to the
Omni.


Stability Requirements: Final Calibration of

Flow Computer
Contents
information contained in Instructions ......................................................................................................... 1
Volume 1, and is applicable
to Revision 20.70/24.70+.
Scope
published with a different
page layout.
All Omni 6000/3000 Flow Computers have calibration stability requirements.
Abstract
Because of the temperature sensitivity and bit resolutions of the A/D and D/A
converters, and the high accuracy requirements, it is important that the following
procedures are followed when calibrating flow computer I/O circuits.
Instructions
(1) Adjust the power supply to give 5.05-5.10 volts at backplane test points.
(2) All final calibrations must be performed using the matching set of combo
Getting Tech Support - modules and power supply module (i.e. changing the power supply or
Technical support is adjusting the voltage during the final calibration requires that a sample
available at:
calibration made up to that point be checked. If there is a noticeable
(281) 240-6161
change, all calibrated points should be rechecked).
the WEB Page at: (3) Before calibrating, eliminate temperature gradient errors by closing the
www.omniflow.com box and allowing at least 20 minutes for temperature stabilization to
or email to: occur. Ensure that unit is not in a high air draft area (i.e. in the path of a
techsupport@omniflow.com fan or AC duct) Make adjustments such as jumper repositioning quickly.
Wherever possible keep the unit closed to retain internal heat. Board
replacements will require that sufficient time be allowed to achieve
temperature stability.
(4) Observe temperature stability requirements of any equipment used in the
calibration process (i.e., current and voltage generators, digital
voltmeters etc.).
TB-970701 ALL.70+ 1
2 TB-970701 ALL.70+
Secondary Totalizers Provide Net Volume at

Temperatures Other than 15°C or 60°F
Contents
information contained in Database Location of Second Set of Net Totalizer Data Points .................... 2
Volumes 2, 3 and 4,
applicable to firmware Keypad Entries Needed to Display the Extra Totalizers ................................. 2
revisions 20/24.71+ and
21/25.71+.
page layout.
Scope
All firmware Versions 20/24 and 21/25, Revisions.70+ of Omni 6000/Omni 3000
Flow Computers have secondary net totalizers for when more than one
reference temperature is required.
Abstract
Some times it is necessary to provide net totalizers at more than one reference
temperature.
Following are the Modbus data points that are used to provide secondary net
totalizers in the Omni. Secondary totalizers are calculated real time just like the
normal totalizers.
The secondary totalizers are activated by setting up floating point data point
7699 with the secondary reference temperature required. This data point is
initialized to 0 at a cold start up which effectively disables the extra totalizers
and their appearance on the Omni default reports (obviously, 0° cannot be used
as a second reference temperature).
You may set up 7699 with a simple variable statement. For example: 7699=#68
will provide a second set of net totalizers corrected to 68 degrees. You may also
initialize point 7699 via a one time Modbus write. If you choose to use the
statement method you may remove the statement immediately after you enter it,
but you should probably leave it to serve as a document trail.
Note that the Omni initializes point 7699 to 0.0 on a cold boot. A cold boot
occurs after a ‘Clear All Ram’ command is executed.
TB-970702 ALL.70+ 1
Database Location of Second Set of Net

Totalizer Data Points
CURRENT PREVIOUS CURRENT PREVIOUS
BATCH BATCH DAILY DAY
Meter #1 5196 5198 5197 5199
Meter #2 5296 5298 5297 5299
Meter #3 5396 5398 5397 5399
Meter #4 5496 5498 5497 5499
Station 5896 5898 5897 5899
Keypad Entries Needed to Display the Extra

Totalizers
Getting Tech Support - Secondary totalizers are viewed using the same key presses used to view the
Technical support is normal net totalizers. For example: pressing [Meter] [n] [Net] or [Net] [Meter]
available at:
[n] will display meter ‘n’ net flow rates and totalizers followed by the secondary
(281) 240-6161
net totalizers. Pressing [Meter] [n] [Batch] [Net] will display the batch net
Email should be sent via totalizer followed by the secondary batch net totalizer. Likewise, the Station
the WEB Page at:
secondary totals are viewed using the same key presses that are used to view
www.omniflow.com the normal station net total. Pressing [Net] will display the station net totalizer
or email to:
followed by the secondary net totalizer. Pressing [Batch] [Net] will display the
station batch net totalizer followed by the secondary batch net totalizer.
2 TB-970702 ALL.70+
Using Boolean Statements to Provide

Custom Alarms in the Flow Computer
Contents
Scope ................................................................................................................... 1
Abstract ............................................................................................................... 1
Example: ....................................................................................................................... 2
Scope
User Manual Reference - All firmware revisions Version .70+ of Omni 6000/Omni 3000 Flow Computers
This technical bulletin have the feature of customizing alarms with Boolean statements.
complements the
information contained in the
User Manual, and is
applicable to all firmware
revisions Version .70+.
Abstract
This bulletin was previously The flow computer automatically records and logs many important alarm events
page layout.
and status changes. These events include transducer ‘Low Alarm and High
Alarm’ states and failure of any transducer connected to the flow computer
which is measurement related.
There are instances however where the flow computer user would like to
monitor other internal or external status events that may have nothing to do with
the measurement functions. These alarms may be the result of a digital I/O point
changing state, or the result of a Boolean logic statement or a variable
statement comparison.
Because of this requirement, the last 16 Boolean statements of the flow
computer serve the dual function of evaluating normal logic expressions, and
also providing user configurable alarm messages. The alarm message text to be
logged and displayed can be entered into the expression fields in any of these
last 16 Boolean statements. These statement numbers are, 1057 through 1072
for flow computers with 48 Boolean statements, and 1073 through 1088 for
computers with 64 statements.
Each Boolean statement has an associated status point which is accessed
using the same address as the statement number (Modbus Point 1072 for
instance). The logic state of this status bit normally reflects the logical result of
the statement (1 or 0, true or false). When the statement is used to provide a
custom alarm message it functions in a different manner. To cause an alarm
message to be logged, simply turn on the status point associated with the
message.
TB-970801 ALL.70+ 1
Example:
Getting Tech Support - In this example, the user wishes to monitor a tank level switch that is connected
Technical support is to Digital I/O Point #1. When the tank level is high, the level switch applies 24
available at:
volts to the digital I/O point.
(281) 240-6161
Email should be sent via Digital I/O Point #1 is first assigned to the Dummy Boolean 1700, this reserves
the WEB Page at: the Point as a digital Input . Modbus Point 1001 will simply follow the digital level
www.omniflow.com applied to the terminals of digital point #1. Had it been Digital Point #22, Modbus
or email to: Point 1022 would be affected.
1025: 1072=1001
Move logic value of Digital I/O #1 into Point 1072.
•
•
•
1072: High Level Alarm
Actual ‘alarm text’ which appears in alarm log.
Statement 1025 (above) is used to transfer the logic state of Digital I/O Point #1
to Point 1072, activating the user alarm whenever 24 volts is applied to the input
terminals by the ‘tank high level’ switch contacts.
2 TB-970801 ALL.70+
Omni Flow Computer Modbus Database:

Overview
Contents
information contained in Omni Flow Computer Modbus Database Extents ........................................ 4
Volume 4 “Modbus
Database Address and I/O Driver Concerns When Interfacing to Omni Equipment ......................... 12
Index Numbers”, applicable For Example:............................................................................................................................. 12
to all firmware revisions
Write Single Variable - Modbus Function 06 ............................................................... 12
.70+.
This bulletin was previously Address Ranges - Future Expansion........................................................................... 12
page layout.
Modbus Database -
Modbus function codes are
Scope
shown in hexadecimal All firmware revisions Versions 70+ of Omni 6000/Omni 3000 Flow Computers
th
notation. The 4 digit (from
the right) of the data point
are characterized by a Modbus database structured as described in this
address defines the data technical bulletin.
type.
TB-970802 ALL.70+ 1
Abstract
The following are the data types within the database:
Digital Flag Bits : Also known as Boolean bits, status bits and
command bits. All data points of this type can
be read via Modbus function code 01 and
written to using function codes 05 and 0F .
Function codes 01 and 0F transfer byte
packed data that is sent in the byte order they
are prepared (not word order). Points are
packed eight to a byte, packing from least
significant to most significant Unused bit
positions within a byte are cleared on
transmission from the Omni and ignored by
the Omni when receiving.
Writing to status points is allowed but
normally is pointless as the status point will be
refreshed by the Omni every 500 ms.
Valid addresses for this type of data are:
1XXX i.e. 1101, 1705, 1921 etc.
16-bit Integer Registers : All data points of this type can be read via
Modbus function code 03 and written to using
function codes 06 and 10.
Byte order transmitted is: MS byte then LS
byte.
X3XXX i.e. 3121, 13133 etc.
8-character ASCII Strings : All data points of this type can be read via
function code 10 (note that function code 06 is
not available on this data type).
Byte order transmitted is as you would type it.
4XXX i.e. 4101, 4502 etc.
32-bit Integer Registers : Formatted as two’s complement. All data

points of this type can be read via Modbus
function 03 and written to using function
codes 06 and 10.
Byte order transmitted is: MS byte of MS
word, LS byte of MS word, MS byte of LS
word then LS byte of LS word.
Valid addresses for this data type are: X5XXX
i.e. 5101, 15205 etc.
2 TB-970802 ALL.70+
TB-970802 Omni Flow Computer Modbus Database: Overview
32-bit IEEE Floating Point : All data points of this type can be read via
Modbus function 03 and written to using
function codes 06 and 10.
Byte order transmitted is: Mantissa Sign
bit/Exponent byte, LS Exponent bit/MS
mantissa byte, middle significant mantissa
byte then LS mantissa byte.
Valid addresses for this data type are: X7XXX
i.e. 7210, 17006 etc.
16-character ASCII Strings : All data points of this type can be read via
function code 10 (note that function code 06 is
not available for this data type).
Byte order transmitted is as you would type it.
14XXX i.e. 14001, 14022 etc.
TB-970802 ALL.71+ 3
Omni Flow Computer Modbus Database

Extents
Getting Tech Support - Data within the Omni Flow Computer data base is organized in logical groups.
Technical support is Certain data written to the Omni requires special processing to occur in the
available at:
Omni before it is stored in the data base. Other data is grouped together
(281) 240-6161
because it is related in function i.e. a collection of real-time data for a specific
Email should be sent via process.
the WEB Page at:
www.omniflow.com The list that follows shows the extent of each table or set of data points within
or email to: the data base. Because the sets of data are not connected, data from adjacent
techsupport@omniflow.com sets cannot be read or written in the same poll.
Omni Flow Computer Modbus Database Extents

APPLICABLE
MODBUS
DATA POINT
DATA TYPE FUNCTION CODES COMMENTS
ADDRESS
(HEX)
Used to
Read/Write
03 User-defined read only packet - Omni
native mode.
00001 Mixed
03 (06) (10) User-defined array - Modicon
compatible.
native mode.
00201 Mixed
03 (06) (10) User defined array - Modicon
compatible.
native mode.
00401 Mixed
03 (06) (10) User defined array - Modicon
compatible.
#1 User defined data archive record -
0701 Mixed 03
Firmware Revisions .70+.
0702 Mixed 03
0703 Mixed 03
0704 Mixed 03
0705 Mixed 03
0706 Mixed 03
0707 Mixed 03
0708 Mixed 03
0709 Mixed 03
#10 User defined data archive record
0710 Mixed 03
- Firmware Revisions .70+.
4 TB-970802 ALL.70+
Omni Flow Computer Modbus Database Extents (Continued)

APPLICABLE
MODBUS
DATA POINT FUNCTION CODES
DATA TYPE (HEX) COMMENTS
ADDRESS
Used to
Read (Write)
Alarm/Event Log archive record -

0711 Mixed 03
Audit Log archive record - Firmware
0712 Mixed 03
Revision Versions .70+.
1001
Status &
to 01, (05), (OF)
Command
1099
1101
to Status 01
1199
1201
to Status 01
1299
1301
to Status 01
1399
1401
to Status 01
1499
1501 Point 1600 is a dummy point included
Status &
to 01, (05), (OF) to concatenate tables 15XX and
Command
1699 16XX.
1701
Status &
to 01, (05), (OF)
Command
1799
1801
to Status 01
1899
1901
to Status 01
1999
1301
to Status 01
1399
2001 Reserved for Future Expansion -
to Status 01 currently will return error exception 02
2100 (illegal data address).
2101
to Status 01
2199
2201
to Status 01
2299
2301
to Status 01
2399
TB-970802 ALL.71+ 5

APPLICABLE
MODBUS
ADDRESS
Used to
Read (Write)
2401
to Status 01
2499
2701
Status &
to 01, (05), (OF)
Command
2799
2801
to Status 01
2899
3001
16-bit Integer
to 03, (06), (10)
Register
3099
3101
16-bit Integer
to 03, (06), (10)
Register
3199
3201
16-bit Integer
to 03, (06), (10)
Register
3299
3301
16-bit Integer
to 03, (06), (10)
Register
3399
3401
16-bit Integer
to 03, (06), (10)
Register
3499
3501
16-bit Integer
to 03, (06), (10)
Register
3599
3601
16-bit Integer
to 03, (06), (10)
Register
3699
3701
16-bit Integer
to 03, (06), (10)
Register
3799
3801
16-bit Integer
to 03, (06), (10)
Register
3899
3901
16-bit Integer
to 03, (06), (10)
Register
3999
6 TB-970802 ALL.70+

APPLICABLE
MODBUS
ADDRESS
Used to
Read (Write)

8-character
to 03, (10) currently will return error exception 02
ASCII String
4101
8-character
to 03, (10)
ASCII String
4199
4201
8-character
to 03, (10)
ASCII String
4299
4301
8-character
to 03, (10)
ASCII String
4399
4401
8-character
to 03, (10)
ASCII String
4499
4501
8-character
to 03, (10)
ASCII String
4599
4601
8-character
to 03, (10)
ASCII String
4699
4701
8-character
to 03, (10)
ASCII String
4799
4801
8-character
to 03, (10)
ASCII String
4899
4901
8-character
to 03, (10)
ASCII String
4999
32-bit Integer
to 03, (06), (10) currently will return error exception 02
2s Complement
5101
32-bit Integer
to 03, (06), (10)
2s Complement
5199
5201
32-bit Integer
to 03, (06), (10)
2s Complement
5299
5301
32-bit Integer
to 03, (06), (10)
2s Complement
5399
5401
32-bit Integer
to 03, (06), (10)
2s Complement
5499
TB-970802 ALL.71+ 7

APPLICABLE
MODBUS
ADDRESS
Used to
Read (Write)
5501
32-bit Integer
to 03, (06), (10)
2s Complement
5599
32-bit Integer
2s Complement
32-bit Integer
2s Complement
5801
32-bit Integer
to 03, (06), (10)
2s Complement
5899
5901
32-bit Integer
to 03, (06), (10)
2s Complement
5999
6001
32-bit IEEE Applicable to Firmware Revisions
to 03, (06), (10)
Floating Point 22/26.71+ only.
6099
6101
32-bit IEEE 32-bit, 2s Complement (Firmware
to 03, (06), (10)
Floating Point Revision 23.70+ only).
6199
6201
to 03, (06), (10)
6299
6301
to 03, (06), (10)
6399
6401 32-bit, 2s Complement (Firmware
32-bit IEEE
to 03, (06), (10) Revisions 23.70+ and 22/26.71+
Floating Point
6499 only).
6501
to 03, (06), (10)
6799
6801
to 03, (06), (10)
6899
32-bit IEEE
Floating Point
7001
32-bit IEEE
to 03, (06), (10)
Floating Point
7099
7101
32-bit IEEE
to 03, (06), (10)
Floating Point
7199
8 TB-970802 ALL.70+

APPLICABLE
MODBUS
ADDRESS
Used to
Read (Write)
7201
32-bit IEEE
to 03, (06), (10)
Floating Point
7299
7301
32-bit IEEE
to 03, (06), (10)
Floating Point
7399
7401
32-bit IEEE
to 03, (06), (10)
Floating Point
7499
7501
32-bit IEEE
to 03, (06), (10)
Floating Point
7599
7601
32-bit IEEE
to 03, (06), (10)
Floating Point
7699
7701
32-bit IEEE
to 03, (06), (10)
Floating Point
7799
7801
32-bit IEEE
to 03, (06), (10)
Floating Point
7899
7901
to 03, (06), (10)
Floating Point 20/24.71+ and 22/26.71+ only.
8499
8501
32-bit IEEE
to 03, (06), (10)
Floating Point
8599
8601
32-bit IEEE
to 03, (06), (10)
Floating Point
8699
8701
32-bit IEEE
to 03, (06), (10)
Floating Point
8799
8801
32-bit IEEE
to 03, (06), (10)
Floating Point
8899
8901
to 03, (06), (10)
Floating Point 20.71+ and 22/26.71+ only.
8999
9001
ASCII Text Maximum of sixty-four 128-byte
to 41, (42)
Buffers buffers per data point .
9499
9500
Reserved for Future Expansion - currently will return error exception 02
to
(illegal data address).
13000
TB-970802 ALL.71+ 9

APPLICABLE
MODBUS
ADDRESS
Used to
Read (Write)
13001
16-bit Integer
to 03, (06), (10)
Registers
13299
13301
16-bit Integer
to 03, (06), (10)
Registers
13399
13401
16-bit Integer
to 03, (06), (10)
Registers
13499
13501
16-bit Integer
to 03, (06), (10)
Registers
13599
13601
16-bit Integer
to 03, (06), (10)
Registers
13699
13701
16-bit Integer
to 03, (06), (10)
Registers
13799
13801
16-bit Integer
to 03, (06), (10)
Registers
13899
13901
16-bit Integer
to 03, (06), (10)
Registers
13999
14001
16-character
to 03, (10)
ASCII String
14099
14101
16-character
to 03, (10)
ASCII String
14199
14201
16-character
to 03, (10)
ASCII String
14299
14301
16-character
to 03, (10)
ASCII String
14399
14400
to
15000
15001
32-bit IEEE
to 03, (06), (10)
Floating Point
15299
15300
to
17000
10 TB-970802 ALL.70+

APPLICABLE
MODBUS
ADDRESS
Used to
Read (Write)
17001
32-bit IEEE
to 03, (06), (10)
Floating Point
17399
17401
32-bit IEEE Not applicable to Firmware Revisions
to 03, (06), (10)
Floating Point 22 & 26.
17499
17501
32-bit IEEE Not applicable to Firmware Revisions
to 03, (06), (10)
Floating Point 21/25 & 22/26.
17899
32-bit IEEE
Floating Point
18101
to 03, (06), (10)
18199
18200
to
49999
TB-970802 ALL.71+ 11
I/O Driver Concerns When Interfacing to Omni

Equipment
Most but not all of the data is grouped in blocks of 100 or so data points. These
blocks in many cases are not connected.
Limit requests for contiguous data across different blocks by examining the third
digit from the right of the data point start and end addresses. If the digit is
different break up the poll request.
For Example:
An application requires data from points 7188, 7201 and 7210 to be read and
displayed on screen. An intelligent I/O driver may determine that it is more
efficient to read 23 data points starting with point 7188 and discard the unused
data. In this particular example the Omni will transmit the data for points 7188
through 7199 and blank data will be returned for data points 7200 through 7210
because the data requested is in two different blocks within the Omni. To obtain
the data correctly the I/O driver should determine that point 7188 and point 7201
are in different data blocks (because the third digit from the right changed from a
1 to a 2) and send out two data requests; one request for point 7188 and
another for points 7201 through 7210.
Write Single Variable - Modbus Function 06

Omni software revisions 20.44 and greater implement this function on all 16-bit
and 32-bit data points. Revisions prior to 20.44 implement function 06 on 16-bit
integers only. To maintain compatibility with early Omni software revisions it
may be advisable to use function 10 to write to single data points as well as
multiple data points.
Address Ranges - Future Expansion

Some of the address ranges specified in this document encompass more data
than may be available on all applications at this time, Omni advises that for
future compatibility any software driver developed should be able to support
these address ranges.
12 TB-970802 ALL.70+
Meter Factor Linearization
Contents
information contained in Meter Factor Linearization Function .............................................................................. 2
Volume 2 and Volume 3,
applicable to Firmware
Meter Factor Validation and Control Chart Functions.................................................... 3
Revision 22.70+/26.70+.
page layout.
Scope
Firmware Revisions 22.70+ and 26.70+ of Omni 6000/Omni 3000 Flow
Computers have the feature of Meter Factor Linearization. This feature applies
to Turbine/Positive Displacement Liquid Flow Metering Systems (with Meter
Factor Linearization).
TB-970803 22/26.70+ 1
Abstract
Meter Factor Linearization Function

Getting Tech Support - Flowmeter performance varies depending upon flow rate and fluid viscosity. The
Technical support is flow computer can compensate for this variation in performance by applying a
available at:
meter factor which is determined by interpolation of a ‘base meter factor curve’.
(281) 240-6161
The user develops this base meter factor curve by proving the flowmeter at
Email should be sent via various flow rates and determining the meter factors for those flow rates.
the WEB Page at:
www.omniflow.com A base meter factor curve must be developed for each product or fluid viscosity.
or email to: The curve can consist of from one to twelve meter factor / flow rate points.
The MF is continuously adjusted for Prove Base

flowrate during a delivery. The MF is Flowrate
‘flow weight’ averaged for the batch.
Meter Factor
The flow computer lifts or lowers MF’s are normalized to the

the MF curve based on the MF ‘Prove Base Flowrate’ for
obtained at the latest official validation / comparison and
flowmeter proving. historical archival purposes.
Flowrate
Fig. 1. Base Meter Factor Curve
2 TB-970803 22/26.70+
TB-970803 Meter Factor Linearization
Meter Factor Validation and Control Chart Functions

The second purpose of the base meter factor curve is also to act as a reference
against which any meter factors developed during subsequent provings of the
flowmeter can be compared. As an aid to this comparison the user specifies the
base proving flow rate. This value is the flow rate which is considered to be the
normal for the flowmeter concerned. For comparison purposes, each
subsequent meter factor is normalized to the base proving flow rate and must
pass two tests before it can be implemented. The first test checks that the
calculated meter factor is within some maximum percentage deviation from the
base curve.
The second test verifies that the meter factor when normalized to the base
proving flow rate is within some maximum percentage deviation from the
historical average of the last ‘n’ meter factors. Only normalized and implemented
meter factors are included in the historical average. The number ‘n’ can be one
through 10.
Test 2 - Maximum Deviation Meter Factor at

Allowed From The Average Actual Flowrate
of The Last ‘n’ Meter Factors (Passes Test 1)
Historical Average of
Last ‘n’ Meter Factors
Base MF Curve
Test 1 - Maximum Deviation Meter Factor Normalized to

Allowed From Base Curve Prove Base Flowrate
(Fails Test 2)
Fig. 2. The Function of the Meter Factor Base Curve
TB-970803 22/26.71+ 3
4 TB-970803 22/26.70+
Calculation of Natural Gas Net Volume and

Energy: Using Gas Chromatograph, Product
Overrides or Live 4-20mA Analyzer Inputs of
Specific Gravity and Heating Value
Contents
information contained in Basic Calculations .............................................................................................. 2
Volume 3, applicable to
Revision 23.71/27.71. Critical Configuration Entries Which Affect the Calculation of Net Volume
This bulletin was previously and Energy .......................................................................................................... 2
page format. Density of Air at Base Conditions .................................................................................. 2
Gas Relative Density (SG) ............................................................................................ 3
Gas Heating Value (HV)................................................................................................ 3
Natural Gas Net Volume Key Analyzer Setup Menu Entries Needed ................................................................... 3
and Energy Calculation -
No Gas Chromatograph Used - Manual Overrides Required ..................................................... 3
Natural gas net volume and
Component Analysis Data Obtained From a Gas Chromatograph............................................. 4
energy calculations apply to
Using Manual Overrides for Component Analysis Data.............................................................. 4
all gas flow computers,
Component Analysis Data via a Serial Data Link ....................................................................... 4
(firmware Revisions
Using Live Inputs for Heating Value, Specific Gravity, Nitrogen or Carbon Dioxide ................... 4
23/27.71) shipped after July
1997. These calculations
are considered using a gas
chromatograph, product
overrides, or live 4-20 mA
analyzer inputs of specific
gravity (SG) and heating
Scope
value (HV). Firmware Revisions 23.71+ and 27.71+ of Omni 6000/Omni 3000 Flow
Computers have the feature of Natural Gas Net Volume and Energy Calculation.
This feature applies to Orifice/Turbine Gas Flow Metering Systems. This bulletin
covers natural gas net volume and energy calculations using a gas
chromatograph, product overrides, or live 4-20 mA analyzer inputs of specific
gravity (SG) and heating value (HV).
TB-970804 23/27.71+ 1
Abstract
Getting Tech Support - Gas compositional data needed by the flow computer to calculate flowing
Technical support is density, mass flow and energy flow of natural gas can be obtained from various
available at:
sources. The following describes how the flow computer should be configured
(281) 240-6161
for each possible scenario.
the WEB Page at:
www.omniflow.com
or email to:
Basic Calculations
techsupport@omniflow.com The basic calculations are:
❑ Net Volume = Mass Flow / Density @ Base Conditions (1)
❑ Energy = Net Volume x Heating Value (2)
Density at Base Conditions can be obtained by one of the following methods:

❑ (GC Relative Density) x (Density of Air @ Base Conditions) (3)
❑ (Override Relative Density) x (Density of Air @ Base Conditions) (4)
❑ (Live 4-20mA Relative Density) x (Density of Air @ Base Conditions) (5)
❑ Calculated using Detailed Method of AGA 8 (6)
Heating Value is obtained using one of the following methods:

Heating Value Calculation ❑ GC Analysis HV (7)
- The flow computer always
calculates Heating Value ❑ Manual Override HV (8)
using one of the mentioned ❑ Live 4-20mA HV (9)
standards, even if it is
instructed not to use it. ❑ Calculated using AGA 5, GPA 2172 or ISO 6976
These calculated values are (component analysis required) (10)
stored in the data base and
can be used to compare
against the values obtained Component Analysis Data is obtained from one of the following sources:
from the GC or calorimeter.
7629=Mtr #1 calculated HV ❑ Online Danalyzer or Applied Automation Gas Chromatograph (11)
7630=Mtr #2 calculated HV
7631=Mtr #3 calculated HV ❑ Manual Overrides in the ‘Fluid Data Analysis’ menu (12)
7632=Mtr #4 calculated HV
❑ Serial Communication Link (13)
❑ Live 4-20mA SG, HV, N2 and CO2
(AGA 8 gross calculation methods only) (14)
Critical Configuration Entries Which Affect the

Calculation of Net Volume and Energy
Density of Air at Base Conditions

This entry is in the ‘Factor Setup’ menu. Setting this entry to ‘0’ ensures that ‘gas
density at base conditions’ is calculated using AGA 8. (method (6) previous
page). Entering the ‘density of air at base conditions’ assuming a valid ‘gas
relative density (SG)’ is available (see next paragraph) will override the AGA 8
calculation of ‘gas density at base conditions’. In this case ‘gas density at base
conditions’ is calculated using either method (3), (4) or (5) (previous page).
2 TB-970804 23/27.71+
TB-970804 Calculation of Natural Gas Net Volume and Energy
Gas Relative Density (SG)

This entry is located in the ‘Fluid Analysis Data’ menu. One entry per active
product is required. It is mandatory that this field contain a valid value of ‘SG’ for
all AGA 8 ‘gross’ calculation methods except for 1985 method #4. The data in
this field can be manually entered or, automatically overwritten by a live 4-20mA
input of ‘SG’ if it exists. This entry also serves as the GC ‘SG’ override if a GC is
providing ‘gas relative density (SG)’ and a GC failure occurs.
Entering a minus value in this field will force the flow computer to calculate ‘gas
density at base conditions’ using AGA 8. (method (6) previous page). Entering
the ‘gas relative density (SG)’ assuming a non zero ‘Density of Air @ Base
Conditions’ is entered (see above) will override the AGA 8 calculation of ‘gas
density at base conditions’. In this case ‘gas density at base conditions’ is
calculated using either method (3), (4) or (5) (previous page).
When an AGA 8 detailed method is selected and a GC is used to provide ‘gas
relative density (SG)’, this entry field is ignored unless a GC failure occurs and
the ‘GC Fail Code’ entry is set to ‘Use Override on GC Failure’.
Gas Heating Value (HV)

This entry is located in the ‘Fluid Analysis Data’ menu. One entry per active
product is required. It is mandatory that this field contain a valid value of ‘HV’ for
AGA 8 ‘gross’ calculation method #1 and also AGA 8 1985 methods #2 and #4.
The data in this field can be manually entered or, automatically overwritten by a
live 4-20mA input of ‘HV’ if it exists. This entry also serves as the GC ‘HV’
override if a GC is providing ‘gas heating value (HV)’ and a GC failure occurs.
Entering a minus value in this field will force the flow computer to use a
‘calculated gas heating value (HV)’ calculated using either AGA 5, GPA 2172 or
ISO 6976 ( method (10) previous page). Entering a positive value into the ‘gas
heating value (HV)’ entry will override the AGA 5, GPA 2172 or ISO 6976
calculation of ‘gas heating value (HV)’.
When an AGA 8 detailed method is selected and a GC is used to provide ‘gas
heating value (HV)’, this entry field is ignored unless a GC failure occurs and the
‘GC Fail Code’ entry is set to ‘Use Override on GC Failure’.
Key Analyzer Setup Menu Entries Needed

The following text discusses only those key entries that must be made to ensure
that the right values for component analysis are used in the calculation of Net
Volume and Energy Flow.
No Gas Chromatograph Used - Manual Overrides Required

Select ‘Always Use Fluid Data Overrides’ for ‘GC Fail Code’ in the ‘Analyzer
Setup’ menu. No other entries are needed.
TB-970804 23/27.71+ 3
Component Analysis Data Obtained From a Gas Chromatograph

Select either ‘Never Use Fluid Data Overrides’ or ‘On Fail Use Fluid Data
Overrides’ for ‘GC Fail Code’ in the ‘Analyzer Setup’ menu to ensure that the
GC data is used in place of the ‘Fluid Data & Analysis Data’ overrides’.
Using the ‘GC’ Heating Value and Relative Density. To ensure that the
heating value and relative density calculated by ‘GC’ are used in the
calculations, make sure that component numbers are assigned for the
‘Heating Value’ and ‘Specific Gravity’ entries in the ‘Analyzer Setup’ menu.
The number entered is not critical, simply use the next consecutive numbers
after all the other components are numbered.
Ignoring the ‘GC’ Heating Value and Relative Density. Entering ‘0’ for the
component number for ‘Heating Value’ and ‘Specific Gravity’ entries in the
‘Analyzer Setup’ menu causes the flow computer to ignore the heating value
and relative density sent by the GC and to use the override values entered in
the ‘Fluid Data & Analysis Data’ menu.
Using Manual Overrides for Component Analysis Data

Activate the ‘Fluid Data & Analysis’ entries by selecting ‘Always Use Fluid Data
Overrides’ for ‘GC Fail Code’ in the ‘Analyzer Setup’ menu. No other entries are
needed in the ‘Analyzer Setup’ menu.
Enter the compositional analysis data values into the appropriate fields in the
‘Fluid Data & Analysis’ menu.
Component Analysis Data via a Serial Data Link

Compositional analysis data values should be written into the appropriate
Modbus points normally containing the manual overrides in the ‘Fluid Data &
Analysis’ menu.
Using Live Inputs for Heating Value, Specific Gravity, Nitrogen or

Carbon Dioxide
In the ‘Station Configure’ menu, assign valid I/O points where 4-20mA and/or
Solartron 3096 gravitometer signals will be connected. Input valid scaling factors
in the ‘Station N2 / SG Setup’ menu.
Note that override data fields in ‘Product #1’ entries of the ‘Fluid Data & Analysis
Data’ menu are overwritten by live data values when 4-20mA inputs are used for
HV, SG, N2 or CO2.
4 TB-970804 23/27.71+
Dual Pulse Flowmeter Pulse Fidelity

Checking
Contents
information contained in Installation Practices.......................................................................................... 2
Volumes 1, 3 and 4, and is
applicable to firmware How the Flow Computer Performs Fidelity Checking .................................... 3
revisions 20/24, 22/26 and
23/27 Versions .71+, Correcting Errors ................................................................................................ 3
relating to helical turbine Common Mode Electrical Noise and Transients............................................................ 3
flowmeters.
Noise Pulse Coincident with an Actual Flow Pulse........................................................ 3
published with a different Total Failure of a Pulse Channel ................................................................................... 4
page layout. Alarms and Displays........................................................................................... 4
Pulse Fidelity Checking -

The dual pulse fidelity
Scope
checking feature allows you
to reduce flowmeter
measurement uncertainty
caused by added or missing Firmware Revisions 20/24, 22/26 and 23/27 Versions.70+ of Omni 6000/Omni
pulses due to electrical 3000 Flow Computers have the feature of Dual Pulse Fidelity Checking. This
transients or equipment
failure. feature applies to Turbine/Positive Displacement Liquid and Gas Flow Metering
Systems.
TB-970901 20/24//22/26//23/27.70+ 1
Abstract
Getting Tech Support - The object of dual pulse fidelity checking is to reduce flowmeter measurement
Technical support is uncertainty caused by added or missing pulses due to electrical transients or
available at:
equipment failure. Correct totalizing of flow must be maintained whenever
(281) 240-6161
possible. This is achieved by correct installation practices and by using turbine
Email should be sent via or positive displacement flowmeters which provide two pulse train outputs. In
the WEB Page at:
addition, an E Combo I/O Module must be installed and the correct configuration
www.omniflow.com settings entered in the Omni Flow Computer.
or email to:
techsupport@omniflow.com The two pulse trains are called the ‘A’ pulse and the ‘B’ pulse. In normal
operation, both signals are equal in frequency and count but are always
separated in phase or time. The API Manual of Petroleum Measurement
Standards (Chapter 5, Section 5) describes several levels of pulse fidelity
checking ranging from Level E to Level A. Level A is the most stringent method,
requiring automatic totalizer corrections whenever the pulse trains are different
for any reason.
For all practical purposes, Level A as described in the API document is probably
unachievable. The Omni Flow Computer implements a significantly enhanced
Level B pulse security method by not only continuous monitoring and alarming
of error conditions but also correcting for obvious error situations, such as a total
failure of a pulse train or by rejecting simultaneous transient pulses. No attempt
is made to correct for ambiguous errors, such as missing or added pulses.
These errors are detected, alarmed and quantified only.
Installation Practices
When using pulse fidelity checking, it is assumed that the user begins with and
maintains a perfect noise free installation. The user must ensure that each pulse
train input to the flow computer is a clean, low impedance signal which will not
be subject to extraneous noise or electromagnetic transients. Any regular
occurrence of these types of events must cause the equipment and/or wiring to
be suspect and investigated. Pulse fidelity check circuitry is not intended to
facilitate continued operation with a poor wiring installation which is prone to
noise or transient pickup.
2 TB-970901 20/24//22/26//23/27.70+
TB-970901 Dual Pulse Flowmeter Pulse Fidelity Checking
How the Flow Computer Performs Fidelity

Checking
Hardware on the E Combo I/O Module of the Omni Flow Computer continuously
monitors the phase and sequence of the two pulse trains. It also monitors the
frequency of the pulse trains. The flow computer determines the correct
sequence of flowmeter pulses based on the time interval between pulses rather
than the absolute phase difference. It does this by comparing the leading edges
of both pulse trains at a set clock interval of 16 microseconds. Maintaining a
minimum phase shift between the pulse trains (as indicated below) ensures that
related pulse edges of each channel are, in worst case, at least 5 clock samples
apart.
MAXIMUM PULSE MAXIMUM PHASE

INPUT FREQUENCY SHIFT REQUIRED
1.5 kHz 45 degrees
3.0 kHz 90 degrees
6.0 kHz 180 degrees
Correcting Errors
Missing or added pulses to either pulse train are considered ambiguous errors
and cannot be corrected. However, they are detected with a 100% certainty and
will be counted, eventually causing an alarm. Totalizing will continue using the A
Pulse Train.
Common Mode Electrical Noise and Transients

INFO - A certainty of 85% is Common mode electrical noise and transients occur at the same instant in time
a conservative specification. (during the same clock period) on each pulse channel. They are detected with a
Tests on production units
show that a 95% detection
certainty of 85%*. The certainty can never be 100% because of the slight
is a more typical proportion. differences in time (approximately 2 microseconds) that it takes each pulse to
This is due to the time skew travel through its associated input circuitry. These simultaneous pulses are not
between pulse channels used to totalize flow but are counted and will cause an alarm.
being closer to 1 µsec than
2 µsec.
Noise Pulse Coincident with an Actual Flow Pulse

It is possible that a common mode noise pulse can occur during the same
sample period as an actual flow pulse. In this case, the pulse would be
detected, alarmed and rejected for totalizing, causing a missing pulse.
Statistically though, worst case at 3 kHz pulse input frequency, the odds are
approximately 20:1 that the pulse should be rejected. To not reject the pulse
would mean accepting 20 times as many extra flow pulses. The 20:1 ratio is
based on the ratio of the periodic time of the flow pulses divided by the periodic
time of the sample period (e.g.: 333.3µsec / 16µsec approximately equals 21).
TB-970901 20/24//22/26//23/27.70+ 3
Total Failure of a Pulse Channel

A total failure of either pulse train will be detected with a 100% certainty. The
flow computer will alarm this condition and continue totalizing with the remaining
pulse train as recommended in API MPMS (Chapter 5, Section 5).
Alarms and Displays

To avoid spurious nuisance alarms such as can occur when flow begins, pulse
fidelity checking is disabled until the incoming frequency exceeds a user preset
frequency. Any differences in the two pulse trains will then be accumulated and
used to trigger an alarm when a user preset value is exceeded. Error
accumulations can be displayed or printed at any time. They are reset only at
the start of a new batch. Alarms are time tagged and recorded in the historical
alarm log.
4 TB-970901 20/24//22/26//23/27.70+
Communicating with Honeywell TDC3000

Systems
Contents
information contained in the Communication Method 1: APM / HPM - SIO ................................................... 2
User Manual, and is
applicable to all firmware FTA Array Points ........................................................................................................... 3
revisions Versions .71+. 32-Bit Long Integer Variables ..................................................................................................... 3
Configuring The Omni Flow Computer .......................................................................... 4
Data Grouping Option (a) Custom Data Packet Setup .................................................. 4
Communication Options
with Honeywell TDC3000 Modbus Function Codes Used to Access Custom Packet Data Within The Omni ........ 4
Systems - The Omni flow Data Grouping Option (b) Variable Statement Moves to Scratchpad Variables ............ 6
computer can communicate
with Honeywell TDC3000
Communication Method 2: Programmable Logic Gateway (PLCG) .............. 6
Systems via SIO modules in Selection of Communication Method ............................................................... 8
combination with APM or
HPM modules. PLCG or
CLM modules communicate
directly with the Omni.
Scope
MVIP Testing - The Omni
flow computer has been All firmware revisions Version .71+ of Omni 6000/Omni 3000 flow computers
tested by Honeywell have the capability of communicating with Honeywell TDC3000 Systems. This
Phoenix as part of their
MVIP certification program.
is a new feature that requires specified communication modules.
Contact Honeywell at:
(602) 313-5830
TB-980201 ALL.71+ 1
Abstract
This technical bulletin addresses the various serial communication options that
can be used to transfer data between Omni flow computers and Honeywell
TDC3000 systems. The hardware equipment used and the limitations of each
method are also discussed.
Three types of serial communication modules are available:
1) Serial I/O (SIO) module in combination with either an Advanced Process
Manager (APM) or High Performance Process Manager (HPM) module.
2) Programmable Logic Controller Gateway (PLCG)
3) Communication Link Module (CLM)
MVIP testing was performed using an Omni 6000 and Honeywell module types
(1) and (2) above. Due to the unavailability of equipment and time constraints,
tests were not performed using the CLM module. After MVIP testing it was the
opinion of the Honeywell engineer that communications with the more powerful
and flexible CLM module would pose no problem to the Omni. The nature of the
types of tasks performed by the CLM module usually mean that a certain
amount of custom I/O driver programming is the norm. This being the case, the
CLM is the most flexible but also most expensive connectivity option.
Communication Method 1: APM / HPM - SIO

Getting Tech Support - Honeywell engineers state that with regard to serial communication there are no
Technical support is differences between the APM-SIO connection and the HPM-SIO connection.
available at: This document will target the APM system but all discussion will also apply to
(281) 240-6161 the HPM system.
the WEB Page at: The APM is a I/O rack system used to get I/O signals into the DCS system. It is
http://www.omniflow.com comprised of a plug in APM processor module and various other serial I/O,
or email to: analog I/O and digital I/O plug in modules. The APM rack system can be
techsupport@omniflow.com expanded by adding one or more additional racks. Assuming open slots are
available, up to 16 SIO modules can be connected to each APM system. Each
SIO module is connected to the target equipment via a Field Termination
Assembly (FTA). Each FTA has 2 serial ports with each port individually
configurable as either an RS232 port or 2 wire RS485 port. Port characteristics
are as follows:
❑ Modicon compatible Modbus RTU protocol
❑ Maximum baud rate of 19200 kbps
❑ Data bits 8
❑ Stop bits and parity selectable
2 TB-980201 ALL.71+
TB-980201 Communicating with Honeywell TDC3000 Systems
FTA Array Points

Each FTA has a maximum amount of memory space allocated by the APM. This
memory is organized in 16 blocks called Array Points. In addition, each HPM or
APM is limited to 80 Array points in total that must be shared between all the
SIO modules in its rack system. Each Array Point can therefore hold 512 bits of
data and can hold one type of data variable.
Each Array Point can therefore be configured as one of the following:
512 Coils or Status points.
32 16 bit Short Integer registers
16 IEEE Floating point variables
16 32 bit Long Integer variables (see below)
With a maximum of 16 array points available per FTA it can be seen that data
consolidation and grouping becomes very important. Typical TDC3000-Omni
systems will require a mixture of data types to be exchanged, this further
complicates the configuration process. The user must take care not to waste
valuable memory space by partially filling array points. Try to minimize the types
of variable (e.g.: if you only need to read a few short integers consider
converting them to long integers within the flow computer using variable
statements). The limited number of array points also impacts how many Omni
flow computers can be connected (multi dropped) to each FTA for example:
Most applications require long integer totalizers, IEEE floating point values and
also alarm statuses. This means that at least 3 array points will be needed per
Omni and that assumes that 16 IEEE floats, 16 totalizers and 512 alarms will be
sufficient to transfer all the data needed by the TDC3000 system (extremely
unlikely, as there could be up to 4 meter runs configured).
32-Bit Long Integer Variables

Long integer types are not supported directly by the TDC3000 system. They can
be read as 2 concatenated 16-bit short integers and combined within the
TDC3000 system. The Honeywell cannot write to Omni long integer types
because the Honeywell SIO Modbus protocol does not support Modbus function
code 16 (write multiple registers) for integer registers. The protocol does
however support writing to IEEE Floating point variables. Omni’s experience has
shown that there are very few instances where the TDC3000 system needs to
write long integers within the flow computer. Typical long integer data that there
has been a need to write in the past has been duplicated in IEEE floats as
shown below and on following page.
Long Integer IEEE Float
Meter #1 - Current MF in Use 5113 7796
Station Running Batch Size 5819 7787

Station Next Batch Size 5820 7783
TB-980201 ALL.71+ 3
Long Integer IEEE Float

Meter #1 - Next Batch Size 5820 7783
Meter #2 - Running Batch Size 5825 7788



Configuring The Omni Flow Computer

Setup the flow computer serial port settings to match the Honeywell FTA
settings and make sure to select ‘Modicon Compatible’.
In view of the Honeywell array point limitation it is important to group the data as
efficiently as possible within the Omni flow computer. Two options are available:
1) Custom data packet arrays
2) Move data to flow computer scratchpad variables using Variable
Statements
Method 1 must be used if it will be necessary to both read and write into the
variables. Method 2 can only be used when it is only necessary to read data.
Data Grouping Option (a) Custom Data Packet Setup

The Omni flow computer has 3 custom data packet areas where data can be
grouped. These 3 data areas are addressed starting at Modbus addresses
0001, 0201 and 0401. Configure these data areas by completing the custom
packet setup menus in the flow computer.
When the Omni serial port is set as being ‘Modicon Compatible’ the custom
packet data is read / write accessible by the TDC3000 system. Unlike the FTA
arrays, the Omni does allow mixed data types within a custom data
packet/array. This means that multiple FTA array points can be associated with
one custom packet.
Modbus Function Codes Used to Access Custom Packet

Data Within The Omni
The Omni supports the following Modbus function codes to access custom
packet data:
Read Multiple Registers 03
Write Multiple Registers 16
Write Single Register 06
4 TB-980201 ALL.71+
From the above it can be seen that Boolean variables must be handled
differently when grouped within a custom array. They cannot be accessed using
the normal Modbus function codes 01, 05 and 15. They can be read and written
but as byte packed bits within Registers not as Coils and Status bits. For this
reason it is recommended that writes to Boolean coils be accomplished by using
the normal Modbus function code 05 and writing directly to the database
Boolean point address.
! CAUTION! ! Here is an example showing a typical setup using the custom packet located at
address 0001:
Because Boolean data is
byte packed the user must ADDRESS FTA ARRAY # USED
ensure that the number of
Packet #01 Point # ………… 7101 0001 - 0016 1
Booleans included in the
custom packet are grouped # of Points ………… 8 Total 16 Floats
in such a way as to ensure Packet #02 Point # ………… 7201 0017 - 0032 1
that the packet always # of Points ………… 8
contains an even number of Packet #03 Point # ………… 7301 0033 - 0048 2
bytes (i.e. the function # of Points ………… 8 Total 16 Floats
codes we are using expect Packet #04 Point # ………… 7401 0049 - 0064 2
to be dealing with ‘registers’ # of Points ………… 8
and you can’t have half a
Packet #05 Point # ………… 5101 0065 - 0072 3
register).
# of Points ………… 4
Packet #06 Point # ………… 5201 0073 - 0080 3
# of Points ………… 4 Total 16 Long Int.
Packet #07 Point # ………… 5301 0081 - 0088 3
Packet #08 Point # ………… 5401 0089 - 0096 3
Packet #09 Point # ………… 3101 0097 - 0100 4
Packet #10 Point # ………… 3201 0101 - 0104 4
# of Points ………… 4 Total 16 Short Int.
Packet #11 Point # ………… 3301 0105 - 0108 4
Packet #12 Point # ………… 3401 0109 - 0112 4
Packet #13 Point # ………… 1105 0113 - 0115 5
Packet #14 Point # ………… 1205 0116 - 0118 5 Total 24 Packed
# of Points ………… 48 Bytes
Packet #15 Point # ………… 1305 0119 - 0121 5
Packet #16 Point # ………… 1405 0122 - 0124 5
Packet #17 Point # ………… 0
# of Points ………… 0 These packets are available but
Packet #19 Point # ………… 0 are not used in this example.
The above shows a total of 32 floating points,16 long integers, 16 short integers
and 192 Boolean status bits packed in 24 bytes being mapped in 1 custom data
packet and 5 FTA arrays.
TB-980201 ALL.71+ 5
Data Grouping Option (b) Variable Statement Moves to

Scratchpad Variables
Option (b) is limited to when data needs to be read but not written to. Non
contiguous data is moved into the flow computer scratchpad variables located
at:
Boolean Scratchpad Variables 1501 through 1699
Integer Scratchpad Variables 3501 through 3599
String Scratchpad Variables 4501 through 4599
Long Integer Scratchpad Variables 5501 through 5599
Floating Point Scratchpad Variables 7501 through 7599
User Boolean statements are used to group Boolean bits as follows:
Example:
1025: 1501=1105:1169 Move 64 bits to 1501 through 1564
1026: 1565=1205:1269 Move 64 bits to 1565 through 1628
User variable statements are used to move all of the remaining data types as
follows:
Example:
7025: 7501=7101:7103 Move 3 floats to 7501 through 7503
7026: 7504=7201:7203 Move 3 floats to 7504 through 7506
Communication Method 2: Programmable

Logic Gateway (PLCG)
The PLCG is meant to receive ‘register’ data from PLCs representing unscaled
analog values and 16-bit counters. Functionality is built into the PLCG which
allows the user to easily scale analog inputs of 0-9999 or 0-4095 into
engineering units. Alarm points can also be entered and monitored. This
philosophy is at odds with the Omni flow computer as the vast majority of the
variables within the flow computer are in engineering units requiring no scaling
or alarm checking in the PLCG. In addition most of the data is contained in IEEE
floating point format or 32-bit long integer values.
The Modbus protocol supported by the PLCG unlike the APM-SIO module does
not support reads or writes of IEEE floating point data. The protocol also does
not support multiple register writes which would be required to write data to a
flow computer long integer type.
The PLCG can however be configured to scale other nominal ranges such as 0-
999 of which there are some variables of this type within the flow computer as
shown below:
Mtr#1 Mtr#2 Mtr#3 Mtr#4 Station
Current Gross Flow Rates 3142 3242 3342 3442 3804
Current Net Flow Rates 3140 3240 3340 3440 3802
Current Mass Flow Rates 3144 3244 3344 3444 3806
Current S&W Corrected Flow Rates 3149 3249 3349 3449
Current Temperature 3147 3247 3347 3447 3809
Current Pressure 3146 3246 3346 3446 3808
Current Analog Density 3148 3248 3348 3448 3810
6 TB-980201 ALL.71+
Counter inputs ranging from 0-65535 are treated more generically requiring no
scaling and are usually used for display purposes or are passed to an
Application Module (AM) for processing.
There are two options to monitor totalizing within the Omni flow computer:
1) Read long integer totalizers as two consecutive counter inputs and
combine in the Application Module (AM) as follows:
Totalizer = (high register * 65536) + low register
2) Read specially provided 16 bit integer non-resetable totalizers that roll at
65536 within the Omni data base shown below.
Mtr#1 Mtr#2 Mtr#3 Mtr#4 Station
Gross Totalizer 3143 3243 3343 3443 3805
Net Totalizer 3141 3241 3341 3441 3803
Mass Totalizer 3145 3245 3345 3445 3807
S&W Corrected Net Totalizer 3150 3250 3350 3450
The advantage of option (1) above is that any of the internal totalizers of the flow
computer can be read in this manner and the results displayed by the TDC3000
system will match the flow computer displayed values. Option (2) is limited to
one set of non-resetable totals which are not normally displayed at the flow
computer and are of limited use.
Using ‘Variable Statements’ within the Omni flow computer makes it easy to
convert just about any variable within the flow computers data base into a 16-bit
register that can be ‘read’ by the PLCG as either a counter or an analog
(assuming the data will fit), the only problem being the availability of enough
variable statements (64 are provided).
Example 1: Variable read as counter for display only

7025: 3501=7105*#10 3501 contains M #1 temperature in tenths of
degrees
Example 2: Variable read as unscaled analog 0-4095 representing 50 to 150

°F
7026: 7105-#50 Adjust for 50 degree zero point
7027: 3502=7026*#40.95 100 degree span = 4095, move to scratch
integer 3502
Note that in Example 2 above, no attempt was made to limit the impact of over
or under range values passed to the PLCG. It is the authors understanding that
inputs outside of the expected range cause ‘bad process value’ alarms in the
PLCG.
TB-980201 ALL.71+ 7
Selection of Communication Method

Analysis of the various methods available shows that communications via the
APM-SIO or HPM-SIO are most likely to provide the best solution, providing
reasonable access to the flow computer’s database and requiring no custom
driver programming in the TDC3000 system. Because of the awkward
philosophical fit between the PLCG and flow computer type devices, many of
the built in features of the PLCG (such as scaling and alarming) cannot be used.
For this reason the use of a PLCG is not recommended except for instances
where one already exists in a system and has an open port and an APM or
HPM is not available. The CLM module is potentially the most flexible solution
but the cost impact of any custom software driver development must be
determined. Omni does not know whether a compatible protocol driver exists at
this time, please contact Honeywell for more information in this regard.
8 TB-980201 ALL.71+
Recalculating a Previous Batch within the

Flow Computer
Contents
information contained in Calculations Performed ..................................................................................... 2
Volume 2, Chapter 3
“Computer Batching Using the Flow Computer Keypad to Recalculate a Previous Batch Ticket 3
Operations”, applicable to Step 1............................................................................................................................ 3
Revision 20.71/24.71+.
Step 2............................................................................................................................ 3
Step 3............................................................................................................................ 3
Batch Recalculation - The Step 4............................................................................................................................ 4
batch recalculation feature
allows you to adjust
Step 5............................................................................................................................ 4
quantities of the previous 4 How the Flow Computer Manages the Modbus Database ............................. 5
batches at measurement
locations where Previous Batch Data that Is Writable............................................................................. 6
SG60/API60 and S&W Batch Recalculation Modbus Registers ........................................................... 7
values only become
available after the batch has Meter “n” Batch Recalculation:
been delivered. Applies to Versions 20.71+ and 24.71+................................................................. 7
Meter “n” Batch Recalculation:
Applies to Versions 22.70 and 26.70. ..................................................................... 8
Conclusion .......................................................................................................... 8
Scope
Firmware Revisions 20.71+ and 24.71+ of Omni 6000/Omni 3000 Flow
Computers have the feature of Batch Recalculation. This feature applies to
Turbine/Positive Displacement/Coriolis Liquid Flow Metering Systems (with K
Factor Linearization.
TB-980202 20/24.71+ 1
Abstract
Getting Tech Support - The purpose of recalculating a previous batch is to make batch quantity
Technical support is corrections based on SG60/API60 and Sediment and Water data becoming
available at:
available via sample analysis performed after a batch delivery is complete. At
(281) 240-6161
measurement locations where SG60/API60 and S&W values are not available
Email should be sent via online, sampler devices continuously extract a representative sample of fluid
the WEB Page at:
during a batch. At the end of the batch the sample container is sent for lab
www.omniflow.com
analysis. The data obtained from the analysis report can then be used to
or email to:
recalculate the batch correction factors and therefore batch quantities. Historical
data from these analysis reports is also used to determine what values of
SG60/API60 should be used for real time calculation of future batches that are
known to have similar characteristic. These batches ultimately can also be
recalculated when their actual analysis is determined.
Calculations Performed
❑ The liquid correction factors Ctl and Cpl are first recalculated using the
sample analysis SG60/API60 and the batch flow weighted average
temperature and pressure calculated during the batch.
❑ Gross Standard Volume (GSV) is recalculated using the newly calculated
Ctl and Cpl.
❑ The Sediment and Water correction factor Csw is calculated using the
sample analysis S&W%.
❑ Net Standard Volume (NSV) is recalculated using the recalculated GSV
and Csw factor.
2 TB-980202 20/24.71+
TB-980202 Recalculating a Previous Batch within the Flow Computer
Using the Flow Computer Keypad to

Recalculate a Previous Batch Ticket
CAUTION!
To ensure that previous Step 1

batch data is correctly
recalculated do not Press [Prog] [Batch] [Meter] [n] [Enter] (n = meter run number). The Omni
recalculate a batch close to LCD screen will display:
ending a current batch in
progress.
TIP - Note that only 4 lines METER #1 BATCH

can be displayed at one Print & Reset ?
time. Use the scroll up or Select Prev# Batch
down arrows keys to display
1
additional text.
Enter API60
.0
Enter SG60
.0000
Enter %S&W
.00
Recalculate&Print?
Step 2
Select which previous batch you wish to recalculate. The Omni stores the last 4
completed batches numbered as:
1 = last batch completed

to
4 = oldest batch completed.
Press [↓] to scroll down to “Select Prev # Batch” and enter a number between
1 and 4, depending upon which batch is to be recalculated.
The flow computer moves the selected previous batch data to the ‘previous
batch’ data points within the database (see explanation later in this document)
Step 3
Enter Password when requested.
TB-980202 20/24.71+ 3
Step 4
Scroll to either “Enter API60” or “Enter SG60”. Type in a valid value and press
[Enter].
Step 5
Scroll to “Recalculate & Print?”. Press [Y] and then [Enter].
At this time the flow computer will recalculate the batch data and send the report
to the printer and the ‘Historical Batch Report Buffer’ in RAM memory. Batch
report data can also be captured in ‘Raw Data Archive RAM’ using the trigger
Boolean 1n76. The default batch report shows the batch number as XXXXXX-
XX where the number ahead of the ‘-‘ is the batch number (5n90) and the
number after the ‘-‘ is the number of times that the batch has been recalculated
(3n52). Variable (3n52) is reset to ‘0’ at the end of a batch and increments each
time the batch is recalculated.
4 TB-980202 20/24.71+
How the Flow Computer Manages the Modbus

Database
A pointer mechanism has been utilized which avoids having to have duplicate
data points for every batch report variable for each of the four previous batches.
Only one set of data points for previous batch data are mapped within the
Modbus database. A pointer register is used to determine which set of previous
batch data will be available by accessing the previous batch data points within
the Modbus database.
Using the batch gross totalizer variable as an example, we have:
Note: The second digit of ❑ Modbus address of Current Batch in Progress – Gross Totalizer is 5n01
the index number (indicated
as “n”) defines which meter ❑ Modbus address of Previous Batch – Gross Totalizer is 5n50
run you are working with
❑ Modbus address of Pointer register to select which previous batch is
(i.e., n = 1, 2, 3 or 4).
mapped is 3n51
As the batch progresses, the gross totalizer (5n01) accumulates flow. At the end
of the batch the flow computer performs the following actions:
1) #3 previous batch data replaces #4 previous batch data
4) Current batch data replaces #1 previous batch data
5) Pointer register 3n51 is set to the value ‘1’ so that the Modbus database
addresses for previous batch will access data for the batch just ended.
This ensures that the batch report which prints immediately at the end of
a batch and gets it’s data from the Modbus database, includes the
correct information.
The following table (using the batch gross totalizer as an example) shows
typical data that would be read by accessing Modbus points 5n01 and 5n50.
The data read depends upon the value of pointer register 3n51.
TB-980202 20/24.71+ 5
CURRENT 1ST PREV. 2ND PREV. 3RD PREV. 4TH PREV.

STEP DESCRIPTION BATCH BATCH BATCH BATCH BATCH
5n01 5n50 5n50 5n50 5n50
Value contained in
Pointer register 1 2 3 4
3n51.
1 First batch running. 12340 0 0 0 0
2 First batch ended. 23450 12340 0 0 0
Second batch
3 ended.
34560 23450 12340 0 0
4 Third batch ended. 45670 34560 23450 12340 0
Fourth batch
5 ended.
56780 45670 34560 23450 12340
Fifth batch ended

6 with sixth batch 6123 56780 45670 34560 23450
running.
Previous Batch Data that Is Writable

Except for the data listed below, all data points for previous batch transactions
are ‘read only’ for reasons of data integrity.
METER #1 METER #2 METER #3 METER #4 STATION

SG 60 or Reference
Density (Rev. 24.71)
8508 8608 8708 8808 8908
API 60 Gravity 8519 8619 8719 8819 8919

Sediment and Water
Percentage (BS&W)
8517 8617 8717 8817 8917
Command Boolean which
triggers the recalculation
2756 2757 2758 2759 1798
6 TB-980202 20/24.71+
Batch Recalculation Modbus Registers

Applies to Versions 20.71+ and 24.71+.
METER #1 METER #2 METER #3 METER #4
REGISTERS REGISTERS REGISTERS REGISTERS
Previous 4 Batches 3151 (Previous

3251 (Previous 3351 (Previous 3451 (Previous
per meter run are 4 batches.
4 batches. 1=last 4 batches. 1=last 4 batches. 1=last
held in each of the 1=last batch.
batch, 4=oldest) batch, 4=oldest) batch, 4=oldest)
3n51 registers 4=oldest)
SG60/Density @Ref
8508 8608 8708 8808
Temp.
API60/ 8519 8619 8719 8819
BS&W 8517 8617 8717 8817
Recalculate & Print

2756 2757 2758 2759
(Edge-Triggered)
STATION REGISTERS
Previous 4 Batches for Station are in 3879
3879 (via keypad only)
(1=last batch, 4=oldest)
SG60/Density @ Ref Temp 8908 (via keypad only)
API60 8919 (via keypad only)
BS&W 8917 (via keypad only)
Recalculate & Print (edge-Triggered) 1798
TB-980202 20/24.71+ 7

Applies to Versions 22.70 and 26.70.
METER #1 METER #2 METER #3 METER #4
Note: Always write to 3n51 REGISTERS REGISTERS REGISTERS REGISTERS
or 3879 to specify the
number of retroactive
Previous 4 Batches 3134 (Previous
bbls/m3 to recalculate 3234 (Previous 3334 (Previous 3434 (Previous
per meter run are 4 batches.
before writing to any of the 4 batches. 1=last 4 batches. 1=last 4 batches. 1=last
held in each of the 1=last batch.
above Modbus Points. batch, 4=oldest) batch, 4=oldest) batch, 4=oldest)
3n51 registers 4=oldest)
SG60/Density @Ref
8508 8608 8708 8808
Temp.
API60/ 8515 8615 8715 8815
BS&W 8514 8614 8714 8814
Recalculate & Print

1756 1757 1758 1759
(Edge-Triggered)
STATION REGISTERS
Previous 4 Batches for Station are in 3879
N/A
(1=last batch, 4=oldest)
SG60/Density @ Ref Temp N/A
API60 N/A
BS&W N/A
Recalculate & Print (edge-Triggered) 1798
Conclusion
Note: Setting these The flow computer retains data for the last four completed batches. Only one set
registers via Variable of this data can be accessed at a time. Pointer registers, 3151 Meter Run #1,
Statements is not allowed
and will not produce the
3251 Meter Run #2, 3351 Meter Run #3, 3451 Meter Run #4n and 3879 for
expected results Meter Station are used to determine what set of batch data will be accessed.
API60/SG60 and S&W data can be adjusted and the batch recalculated by
writing a ‘1’ to points, 2756 for Meter Run #1, 2757 for Meter Run #2, 2758 for
Meter Run #3, 2759 for Meter Run #4 and 1798 for Meter Station.
8 TB-980202 20/24.71+
Date: 05 22 03 Author(s): R. D. / I. P. TB # 980803
Upgrading Flow Computer Firmware
Contents
information contained in Safety Considerations ........................................................................................ 2
Volume 1, applicable to all
firmware revisions. This Instructions ......................................................................................................... 3
technical bulletin replaces
and invalidates TB-980301 Installing New OmniCom PC Configuration Software................................................. 3
“Upgrading EPROM Replacing the Central Processor Module (CPU) and EPROM Chips ............................ 4
Chips”.
Resetting RAM .............................................................................................................. 5
Verifying and Updating Information of Installed Modules (Check I/O Modules) ............. 6
▲ IMPORTANT! ▲ Setting the Number of Digits and Decimal Places for Totalizers ................................... 8
Special Instructions If Upgrading from Revision 20.56 Firmware ............................................... 9
After Replacing CPU
Module or EPROMs and Downloading the Configuration File from OmniCom to the Flow Computer.............. 10
Before Downloading Returning the Old EPROMs ........................................................................................ 12
Configuration File - You
must perform the ‘Check
Troubleshooting Tips ....................................................................................... 12
I/O Modules’ procedure Omni Display Does Not Come On After Resetting All RAM ........................................ 12
(see page 6 in this bulletin) Omni Front Panel Display is Blinking and/or the Keypad is Locked ............................ 13
and calibrate your analog
I/Os before downloading “Cannot Open File” Message is Displayed when Trying to Transmit the Saved Report
the configuration file to the Templates to the Omni ................................................................................................ 13
upgraded flow computer. Incorrect Data in Printed Customized Reports ............................................................ 13
Also, you must reset RAM
Unable to Complete a Prove Sequence ...................................................................... 13
as expressed in this
technical bulletin before OmniCom Unable to Communicate to the Flow Computer.......................................... 14
downloading the
configuration file. These
procedures must be
Scope
performed whether or not a
corresponding message is
displayed on the front panel
LCD screen of the flow This technical bulletin is applicable to all firmware revisions of Omni 6000/Omni
computer. Failure to do so 3000 Flow Computers. The information contained in this technical bulletin is
may void the warranty and
cause future problems and targeted to qualified professionals only.
unpredictable results with
your flow computer.
TB-980803 All Revs 1

Abstract
DANGER! Upgrading Omni flow computer firmware allows users to incorporate new
features and increase the capabilities of their flow metering system application.
An upgrade may also be necessary for system conformance to API standards
and Year 2000 (Y2K) requirements.
To upgrade your flow computer firmware you will need to perform certain critical
steps, such as:
Electrical Shock Hazard!
Dangerous AC voltages are ❑ Install new version of OmniCom Configuration PC Software.
present on the power supply
module and ribbon cable ❑ Save flow computer configuration file and report templates.
when the unit is AC
powered. To avoid electrical ❑ Replace Central Processor Module or EPROM chips.
shock which could be fatal,
It is imperative that you ❑ Reset RAM.
remove all power before
opening and disassembling ❑ Set the number of digits and decimal places for totalizers and factors.
the flow computer and take
any other necessary ❑ Download and adjust flow computer configuration file and report
precautions. templates.
Only qualified technicians
should work on any internal
circuitry. Omni Flow
Computers, Inc. is not Safety Considerations
responsible for personal
injuries or accidents that Before removing any circuit boards from the flow computer, the following must
may occur when working on be observed:
flow computer circuitry.
❑ Personal Safety : Although most of the internal circuits are powered by
▲ CAUTION! ▲ relatively low voltages, dangerous AC voltages are
present on the power supply module and ribbon
Static electricity can cable when the unit is AC powered. For this reason
damage flow computer
circuitry. Take approved it is important to remove all power before
static device handling disassembling the computer.
precautions when working
on the flow computer. ❑ Static Electricity : Static electricity can be generated simply by moving
around on certain surfaces or wearing certain types
of clothing. The flow computer’s printed circuits can
be damaged by this static electricity. Take approved
static device handling precautions when working on
the flow computer.
2 TB-980803 All Revs

TB-980803 Upgrading Flow Computer Firmware
Instructions
Before removing the Central Processor Module (CPU) or old EPROMs, you
must install the new version of OmniCom Configuration PC Software supplied
with your new CPU or EPROMs and use this new version to retrieve the
configuration file from the flow computer.
Installing New OmniCom PC Configuration Software

Using OmniCom Help -
Context sensitive help is (1) With the old EPROMs still in the flow computer, install the new
available by pressing the OmniCom to your PC from the diskette shipped with the CPU or
[F1] key on your PC EPROMs. The diskette label provides installation instructions.
keyboard when running
OmniCom.
(2) Create a new file from within the newly installed version of OmniCom by
opening ‘File/New’ and entering the file name.
(3) When prompted for the EPROM version number of the file to create,
select the version number that corresponds to the NEW EPROMs you
will be installing.
(4) Upload the configuration file from the OLD set of EPROMs installed in
the flow computer by opening ‘Online/Start Comm’ and selecting
‘Receive Omni Configuration Data’.
(5) Subsequently, receive ALL the report templates by selecting ‘Receive

Report Templates’ within the ‘Online/Start Comm’ menu. As a
precautionary measure, this should be done regardless of whether or
not default report templates are being used.
(6) Print the configuration file from OmniCom by opening ‘File/Print’ and
selecting your print option (‘Yes’ or ‘No’).
(7) Verify all settings indicated in the configuration file printout and make
any necessary adjustments to these settings that are appropriate for
your particular application.
(8) Close OmniCom by selecting ‘Exit’ from the ‘Print’ menu. You will be
prompted on whether to save the configuration file and each of the
report templates. Answer ‘Yes’ to all.

Replacing the Central Processor Module (CPU) and

EPROM Chips
▲ CAUTION! ▲
(1) If you are replacing ONLY the EPROM chips and NOT the CPU
When removing the CPU module, reset all RAM in the Omni via the front panel keypad. If you will
Module, take extreme care be replacing the entire CPU module, DO NOT reset the RAM.
not to bend or fold the
membrane keypad ribbon To reset RAM from the front panel keypad, press [Prog] [Setup]
cable too sharply, or the [Enter] [Enter] [Enter], then type in your privileged password as
metallic traces could be
damaged. prompted. Scroll down by pressing the [È] key to the ‘Reset All Ram?’
prompt and answer [Y] to answer ‘yes’. Answer ‘Yes’ or ‘OK’ to any
Location of EPROM warnings. (Go to Step 14 for detailed instruction on resetting Ram.)
Chips- The location of the
EPROM chips on the CPU
Module is shown in Fig. 1. (10) Remove power from the Omni flow computer and remove the CPU
The EPROMs are the two module.
large 32-pin Integrated
Circuits (ICs or “chips”) with
labels marked U3 and U4. (11) Make note of the new EPROM version and checksum indicated in the
Note the position of the label placed on the EPROM chips. You will need this information later.
orientation notches at one
end of each EPROM.
(12) Either replace the old CPU module with a new CPU that has the new
▲ IMPORTANT! ▲ set of EPROMs, or simply replace the old set of EPROMs with the new
set.
Replacing EPROM Chips -
Ensure that all pins plug into
there respective holes and (13) After replacing or reinstalling the CPU module, apply power to the Omni
that none are bent. flow computer. Make a note of what your LCD screen displays when
powering up. If you receive a display indicating loss of calibration data,
▲ IMPORTANT! ▲ you will need to calibrate your analog I/Os after completing the EPROM
upgrade. (Refer to Volume 1 “System Architecture and Installation”
After Replacing CPU of the User Manual for more information.)
Module or EPROMs and
Before Downloading
I/O Modules’ procedure
Math
(see page 6 in this bulletin) Central Program Program Archive
Processor
and calibrate your analog Processor EPROM RAM RAM
I/Os before downloading
the configuration file to the
upgraded flow computer.
technical bulletin before
downloading the
configuration file. These Backup
procedures must be Batttery
LCD screen of the flow
computer. Failure to do so EPROM Size
may void the warranty and 1 OR 4 Meg Bit System Watchdog
cause future problems and Select 4 Meg J3 In = Enabled
unpredictable results with As Shown J3 Out = Disabled
your flow computer. J1 J2 (Always Enabled)
J3
Figure 1. Layout of Central Processor Module Showing Location of

EPROM ICs and Jumpers J1, J2 and J3.

Resetting RAM
▲ IMPORTANT! ▲ (11) You will need to reset RAM before and after replacing EPROM chips. If
After Replacing CPU you will be replacing the entire CPU module, reset RAM only AFTER
Module or EPROMs and replacing the CPU. DO NOT reset the RAM before replacing. When
Before Downloading power is applied to the flow computer after replacing EPROM chips, the
must perform the ‘Check following screen is displayed:
(see page 6 in this bulletin) RAM Data Invalid
and calibrate your analog
I/Os before downloading
Reconfigure System
the configuration file to the
Using “OMNI” as
upgraded flow computer. Initial Password
technical bulletin before Enter the key press sequence [Prog] [Setup] [Enter] [Enter] [Enter]
downloading the and the following screen is displayed:
procedures must be
performed whether or not a PASSWORD
corresponding message is MAINTENANCE
displayed on the front panel Privileged _
LCD screen of the flow Level 1
computer. Failure to do so Level 1A
cause future problems and
unpredictable results with Different screens will be displayed each time you press enter before you
your flow computer. reach the above screen.
Program Mode - Pressing (15) At the ‘Privileged’ prompt, enter the following key press sequence to
the [Prog] key will activate use ‘OMNI’ as the privileged password: [Alpha Shift] [Alpha Shift] [O]
the Program Mode. While in
this mode, the Program LED [M] [N] [I] [Enter]. The cursor will move down to the next entry.
above the keypad is lit red.
To exit the Program Mode,
PASSWORD
press the [Prog] key
repeatedly until the Program
MAINTENANCE
LED goes off. Privileged OMNI
Level 1 _
Level 1A
(16) Scroll down by pressing repeatedly the [È] key to ‘Reset All Ram?’ and
press [Alpha Shift] [Y] [Enter] for ‘Yes’.
PASSWORD
MAINTENANCE
Archive Run?(Y/N)
Reset All Totals
Reset All Ram ?
Y
The display will briefly go blank, the backlight will go off and come back
on. The following screen may then reappear:
RAM Data Invalid

Reconfigure System
Using “OMNI” as
Initial Password

(17) Press [Status] and a screen similar to the following will be displayed:
Module S-Ware H-
Ware
B-1 Y Y
E-1 Y Y
D-1 Y Y
(18) Scroll down by pressing repeatedly the [È] key to the end to display the
Revision Number and EPROM Checksum.
Module S-Ware H-
Ware
S-1 Y Y
Revision No.
021.72
EPROM Checksum
2408
Verify that these match with what you previously noted in Step 11. If
they do not match and there is an EPROM Checksum alarm, stop at this
point and contact Omni technical support.
▲ IMPORTANT! ▲
Verifying and Updating Information of Installed Modules
After Replacing CPU
Module or EPROMs and (Check I/O Modules)
Before Downloading
(19) If the EPROM Revision number and Checksum are correct, verify if both
I/O Modules’ procedure and the ‘S-Ware’ (Software) and ‘H-Ware’ (Hardware) columns read ‘Y’
calibrate your analog I/Os (Yes) for all the installed modules before proceeding any further. Scroll
before downloading the up and down the screen in the previous step by using the [È] / [Ç]
configuration file to the
upgraded flow computer.
arrow keys to view installed modules. If both columns read ‘Y’, go to
Also, you must reset RAM Step 25. If not, proceed to the following step (20).
downloading the Module S-Ware H-
configuration file. These Ware
procedures must be B-1 Y Y
performed whether or not a E-1 Y Y
corresponding message is D-1 Y N
displayed on the front panel S-1 N Y
LCD screen of the flow Revision No.
computer. Failure to do so 021.72
may void the warranty and EPROM Checksum
2408
your flow computer.
Program Mode - Pressing (20) If one or more of the installed modules reads ‘N’ (No) under the ‘S-
the [Prog] key will activate
the Program Mode. While in
Ware’ (Software) and/or ‘H-Ware’ (Hardware) columns, press [Prog]
this mode, the Program LED [Setup] [Enter] [Enter] and the following is displayed:
press the [Prog] key *** MISC. SETUP
repeatedly until the Program ***
LED goes off. Password Maint?(Y)
_
Check Modules ?(Y)

Config Station?(Y)
Different screens will be displayed each time you press enter before you
reach the above screen.

(21) Move the cursor down by pressing the [È] key to ‘Check Modules?’.
*** MISC. SETUP

***
Password Maint?(Y)
Check Modules ?(Y)
_
Config Station?(Y)
(22) Press [Enter] and a screen similar to the following is displayed:
Module S-Ware H-
Ware
B-1 Y Y
E-1 Y Y
D-1 Y N
(23) Scroll down by pressing repeatedly the [È] key to ‘Update S-Ware?’
and press [Alpha Shift] [Y] [Enter] to enter ‘Y’ for ‘Yes’.
Module S-Ware H-
Ware
D-1 Y N
S-1 N Y
Update S_Ware ?
Y
You will be prompted to enter your password. Also enter ‘Y’ to answer
‘OK’ if cautioned that updating the software will cause the I/O
configurations to be cleared.
(24) Exit the Program Mode when you are done by pressing the [Prog] key
repeatedly until the Program LED above the keypad goes out. This
returns you to the Display Mode.
Setting the Number of Digits and Decimal Places for

Totalizers
(25) In newer versions of EPROMs, you are given an option to set the
number of digits for cumulative totalizer rollover (8 or 9 digits) and the
number of decimal places for volume and mass totalizers. Set these
options via keypad ONLY by pressing [Prog] [Setup] [Enter] [Enter]
[Enter]. The following screen is displayed:
PASSWORD
MAINTENANCE
Privileged _
Level 1
Level 1A

(26) At the ‘Privileged’ prompt, enter the following key press sequence to
use ‘OMNI’ as the privileged password: [Alpha Shift] [Alpha Shift] [O]
[M] [N] [I] [Enter]. The cursor will move down to the next entry.
Setting the Number of
Digits for Totalizers - PASSWORD
Totalizers within the flow MAINTENANCE
computer can be rolled at 8 Privileged OMNI
or 9 significant digits. To set Level 1 _
totalizer rollover to 9 digits, Level 1A
press [0] [Enter]. To set
totalizer rollover to 8 digits,
press [1] [Enter].
(27) Scroll down by pressing repeatedly the [È] key to ‘Reset All Totals?’.
Setting Volume and Mass
Totalizer Resolution - PASSWORD
Gross and net volume and MAINTENANCE
mass totalizer values can Reconfig Archive ?
be expressed with up to 3 Y
decimal places. To set the Archive Run?(Y/N)
number of decimal places N
for totalizer resolution, press
the corresponding number
Reset All Totals ?
key ([0], [1], [2] or [3]
_
decimal places, where
0=Klbs, 1=100lbs, 2=10lbs,
3=lbs). Then press the
[Enter] key. All firmware
(28) Press [Alpha Shift] [Y] [Enter] for ‘Yes’ and a screen similar to the
revisions, except for Version following is displayed:
20.56, provide Mass in
pounds.
All Totals Now
Reset
Help for Number of Digits Totalizer
and Decimal Place Resolution
Settings - You can view the # Digits, 0=9, 1=8
Help in OmniCom under 0
“Factor Setup & Sys DecPlacesGross&Net
Constants” by highlighting 0
each of the fields. Then use DecimalPlaces Mass
F1 for a detailed explanation 3
of each of your choices.
However, DO NOT set
these options via OmniCom. Enter the respective values you want for each and every totalizer
Context-sensitive help is resolution setting and press the [Enter] key after each entry (see
also available via the Omni
front panel keypad by
sidebar).
pressing the [Help] key
It is strongly recommended that you set these resolutions NOW
(same as the [Enter] key)
rapidly twice while the because you will not be able to change these settings after configuring
cursor is at the entry you your flow computer or during flow operations without resetting to zero all
want to set. your totalizers.
Special Instructions If Upgrading from Revision 20.56

Firmware
Version 20.56 EPROMs provide Mass in hundreds of pounds. If you
want to continue receiving your Mass in hundreds of pounds, press [1]
[Enter] at the ‘DecimalPlaces Mass’ entry.
repeatedly until the Program LED above the keypad goes out. This
returns you to the Display Mode.

Downloading the Configuration File from OmniCom to

the Flow Computer
Program Mode - Pressing
the [Prog] key will activate (24) In the Display Mode, press [Prog] [Setup] [Enter] [Enter] to display the
the Program Mode. While in ‘Misc. Setup’ menu.
this mode, the Program LED
To exit the Program Mode, *** MISC. SETUP
press the [Prog] key ***
repeatedly until the Program Password Maint?(Y)
LED goes off. _
Check Modules ?(Y)
Config Station?(Y)
(31) Scroll down by pressing repeatedly the [È] key to ‘Serial I/O “n”’.
*** MISC. SETUP

***
User Display ? “n”
Config Digital“n”
Serial I/O “n”
_
Enter the number of the flow computer serial port to which your
OmniCom PC is connected and press [Enter]. A screen similar to the
following will display:
SERIAL PORT #2
Baud Rate
38400
Number of Data Bit
8
Number of Stop Bit
1
▲ IMPORTANT! ▲
(32) Scroll down to ‘Modbus ID’ and then to ‘Modbus Type’ and enter the
It is recommended that you corresponding settings indicated in the OmniCom configuration file you
select ‘Modbus RTU printed earlier. Remember to press [Enter] after typing each setting.
(modem)’ protocol for the
‘Modbus Type’ in Step 32 if
it is available in your new SERIAL PORT #2
EPROM version. If you TX Key Delay
decide to use this protocol, 1
ensure that you make this Modbus ID
same change in your 1
OmniCom configuration file
Modbus Type
under ‘Config Serial I/O’
before proceeding to
2
download the configuration
file to the Omni
(33) Run OmniCom and open the configuration file you saved earlier which
pertains to this flow computer. Open the File Menu and select ‘Print’.
Print the file to a printer on your PC to have an updated printout of the

flow computer configuration.
(34) Open ‘Offline/Omni Configuration/Config Serial I/O’ and ensure that

the ‘Modbus Type’ is set correctly to match what you selected in Step
32.

(35) Open ‘Online/Start Comm’. Check the Modbus ID, Comm Port, Baud
Rate, and Comm Media settings to ensure that these are correct. If you
set the port in Step 32 to ‘Modbus RTU (modem)’ protocol, ensure that
‘Comm Media’ is set to Modem.
(36) Transmit Omni Configuration Data.
(37) Transmit Omni Report Templates.
(38) Calibrate your analog I/Os if you are required to do so. For more
information on calibrating analog I/O, see Volume 1, Chapter 8 of the
User Manual.
Returning the Old EPROMs

You are now done. Remember to use the Business Reply Label supplied with
your new EPROMs. If you have not yet completed your EPROM Upgrade Form,
please do so now and return along with the old EPROMs to Omni Flow
Computers, Inc.
Troubleshooting Tips
Omni Display Does Not Come On After Resetting All RAM

Tech Support - If you If the Omni Display does not come on after resetting all RAM, proceed as
encounter any other follows:
difficulties, please contact
our technical staff.
(1) Disconnect all power to the Omni.
Phone: (281) 240-6161
Fax: (281) 240-6162 (2) Remove CPU Module and also remove the System Watchdog Jumper
E-mail: J3 (See Figure 1) on the CPU.
(3) Reinstall CPU Module with Jumper J3 removed.
(4) Power up the Omni and reset all RAM again. Display should be on.
▲ IMPORTANT! ▲
(5) Power down again the flow computer and remove CPU Board.
Replacing RAM and
EPROM Chips - Ensure (6) Replace Jumper J3 and then reinstall the CPU Module.
that all pins plug into there
respective holes and that (7) Once again, apply power to the flow computer.
none are bent.
The Omni display should now be normal. However, if problem persists, try
unplugging and reconnecting the RAM chips into the CPU board as follows:
(2) Remove CPU Module.
(3) Unplug and reconnect RAM chips to the CPU board
(4) Reinstall the CPU Module.
(5) Power up the Omni and reset all RAM again. Display should be normal.

Omni Front Panel Display is Blinking and/or the Keypad

is Locked
This problem may be solved by unplugging and reconnecting the RAM chips
into the CPU board as follows:
(3) Unplug and reconnect RAM chips to the CPU board
(5) Power up the Omni and reset all RAM again. Display should be normal.
“Cannot Open File” Message is Displayed when Trying to

Transmit the Saved Report Templates to the Omni
Sometimes, when trying to transmit the saved report templates to the flow
computer, OmniCom will display a message indicating that it cannot open the
file. Simply go to the OmniCom pull-down Report menu and open each of the
reports individually, make the necessary changes and resave the reports. The
change can simply represent change to the same thing it was before.
Subsequently, save the template (usually ALT-S). Exit OmniCom and then
restart OmniCom. Open the file and try transmitting the templates to the Omni
again.
Incorrect Data in Printed Customized Reports

When upgrading EPROMs and using customized reports, the data in the printed
report may not be correct because some of the database registers may have
changed, moved or redefined in the new version with respect to the old version.
If you see that the printed data is not what you expected, then you should open
the report template files to check if you are retrieving the data from the correct
registers for the new EPROM version. Also verify with OmniCom that “Use
Default Report Template’ under ‘Printer Setup’ is set to ‘No’.
Unable to Complete a Prove Sequence

Sometimes you are unable to get through a prove sequence after an EPROM
upgrade. Open up the deviation percentages in the Prover Setup to establish
an initial prove sequence. Once a prove sequence has been established, you
can tighten up the deviation percentages to what you had set before the
EPROM upgrade.

OmniCom Unable to Communicate to the Flow Computer

Sometimes you are unable to communicate to an Omni after replacing the
EPROMs. This may be caused by the following:
❑ The OmniCom Start Comm/Comm Media setting differs from the Omni
flow computer Modbus Type setting in the serial port setup. In the newest
versions of EPROMs when the flow computer is powered-up, the
EPROMs default to Modbus RTU (modem) for Serial Port # 2. The
Modbus RTU (modem) protocol is the preferred protocol; therefore, make
this change in your OmniCom configuration file AND also set the ‘Comm
Media’ to ‘Modem’ in the ‘Online/Start Comm’ menu.
❑ The new EPROMs default to Modbus ID 1 on power-up. Ensure that your
Modbus ID matches in both the ‘Online/Start Comm’ menu and in the
serial port setup in the Omni. Also ensure the OmniCom configuration
file, Omni serial port, and OmniCom ‘Start Comm’ screen are all set to the
same Modbus ID.

Peer-to-Peer Basics
Contents
information contained in Determining Which Computer Will Be Master ................................................. 2
User Manual, and is
applicable to all firmware Communication Settings for the Peer-to-Peer Link ........................................ 3
revisions Version .70+.
This is an updated edition
Foreign Modbus Devices and Single Master Systems ................................... 3
that replaces previously Wiring Options .................................................................................................... 4
published bulletins under
the same title. RS-232-C Wiring Requirements .................................................................................... 4
See also the following: RS-232 to RS-485 Converter Wiring Requirements ...................................................... 5
❑ TB-980402 - Using the RS-485 Wiring Requirements........................................................................................ 6
Peer-to-Peer Function in Setting up Transactions..................................................................................... 8
a Redundant Flow
Computer Application What Modbus Function Codes Are Used ......................................................... 8
❑ Volume 1 - 1.6.3. Serial Special Considerations when ‘Modicon Compatible’ is Selected for Port #28
Communication Modules
Using Peer-to-Peer with Micro Motion Coriolis Mass Meters ..................... 9
The Micro Motion Meter is a Modicon Compatible Device........................................... 11
Peer-to-Peer
Communications - The Setting Up the Peer-to-Peer Transactions ..................................................... 11
peer-to-peer communication
feature allows you to multi-
drop up to 32 flow
computers and other
devices in RS-485 serial
communications mode, and
up to 12 using RS-232-C
communications.
Scope
All firmware revisions Version .70+ of Omni 6000/Omni 3000 Flow Computers
have the Peer-to-Peer Communication feature.
Peer-to-Peer Redundancy
Schemes - Redundancy
schemes allows for
uninterrupted measurement
and control functionality by
interconnecting two
identically equipped and
configured flow computers.
TB-980401 ALL.70+ 1
Abstract
Getting Tech Support - Communications between Omni flow computers is accomplished using the peer-
Technical support is to-peer function. This function is available only on Serial Port #2 with data being
available at:
transmitted and received using Modbus RTU protocol. A data transaction list
(281) 240-6161
within each flow computer defines each Read or Write operation to be
Email should be sent via transacted for that computer. A maximum of 16 transactions per flow computer
the WEB Page at:
are available. The transaction list must be contiguous (i.e., an empty transaction
www.omniflow.com
will be treated as the end of list).
or email to:
techsupport@omniflow.com Two optional serial communication I/O modules are available with your flow
computer: the RS-232-C (compatible) Model #68-6005, and the RS-232-C/RS-
485 Model #68-6205. The older Model #68-6005 is only capable of RS-232
compatible serial communications. The newer Model #68-6205 is capable of
either RS-232 or RS-485 communications via a selection jumper. When
jumpered for RS-232, the characteristics and functionality of this module is
identical to that of the older RS-232-C module.
Determining Which Computer Will Be Master

Each flow computer wishing to communicate must temporarily become a
Modbus Master so that messages may be initiated and its transaction list
processed. This is accomplished when the current Modbus Master completes its
transaction list and broadcasts the Modbus address of the next computer to be
the master. The computer with the Modbus ID which matches the broadcast
then assumes mastership and proceeds to process its transaction list. A time-
out occurs whenever the next master in sequence does not take mastership and
the broadcast will be retried once. Should the computer still fail to respond, the
current master will attempt to pass mastership to the next computer in sequence
by incrementing the Modbus ID by one and re-broadcasting the new Modbus ID.
Each flow computer needing to process a transaction list (i.e., be a master)
requires the following three entries: (1) Next Master in Sequence; (2) Last
Master in Sequence; and (3) Retry Timer (50mS ticks).
These entries are in the Peer-to-Peer Setup menu and function as follows:
Entry 1 : This entry is the Modbus ID for the next flow computer master. A
non zero entry here is what actually turns on the peer-to-
peer function. Modbus ID’s for master devices in the link must
be assigned starting at 1, and for maximum efficiency not contain
any missing ID’s (i.e., 1, 2, 3, 4, Not 1, 3, 6, 10, for instance).
Entry 2 : This entry is the Modbus ID for the last flow computer master.
Any master failing to find the ‘next master’ will keep trying
Modbus ID’s until it reaches this ID, it will then start the search
again at Modbus ID 1.
Entry 3 : This entry is used to setup the communication retry rate. When
the peer-to-peer link is solely comprised of Omni flow computers
this entry should be set to 5 ticks (150 msec).
2 TB-980401 ALL.70+
TB-980401 Peer-to-Peer Basics
Communication Settings for the Peer-to-Peer

Link
The following settings must be used:
❑ Modbus RTU Protocol
❑ 8 Data Bits
❑ 1 Stop Bit
❑ No Parity
While slower baud rates can be used, 38.4 kbps or 19.2 kbps will provide
maximum performance.
Foreign Modbus Devices and Single Master

Systems
INFO - It is important to note The peer-to-peer function is not limited to multiple Omni flow computers. Some
that in a peer-to-peer applications simply require a single flow computer master to communicate with
system, only the flow
computers that have a non-
a variety of Modbus slave devices which may be flow computers, PLC’s etc. In
zero entry for ‘Next Master these cases, the entries 1 and 2 above would be set to 1 in the master flow
in Sequence’ are limited to computer only, signifying only one master is in the system. Entry 3 above would
using Serial Port #2, all of normally be set to 3 but may need to be increased depending upon the
the other flow computers
are simply acting as
message response time of any foreign Modbus devices in the system.
Modbus slaves and can use
any valid Modbus serial
port.
TB-980401 ALL.70+ 3
Wiring Options
RS-232-C Wiring Requirements

The following diagram shows the wiring requirements using the RS-232-C
termination option. When multiple flow computers are used as peer-to-peer
masters, they are connected in two-wire, multi-drop mode.
INFO - The Omni Flow
Computer uses a
proprietary ‘tristatable’
RS-232-Compatible serial
port, which unlike a normal
RS-232 port, can be multi- Om ni #1 Om ni #2 Om ni #3 Om ni #4
dropped, interconnecting up TB3 TB3 TB3 TB3
to 12 flow computers or
(TB2) (TB2) (TB2) (TB2)
other serial devices.
1 1 1 1
2 2 2 2
3 3 3 3
4 4 4 4
5 5 5 5
6 6 6 6
7 7 7 7
8 8 8 8
9 9 9 9
10 10 10 10
11 11 11 11
12 12 12 12
Fig. 1. Omni 6000 (3000) Peer-to-Peer Wiring Requirements using the

RS-232-C Termination Option
4 TB-980401 ALL.70+
RS-232 to RS-485 Converter Wiring Requirements

The following diagram shows a typical installation where two flow computers are
connected to a PLC via an RS-232 to RS-485 converter module.
Omni #1 Omni #2
TB3 TB3
(TB2) (TB2)
1 1
2 2
3 3
4 4 RS-232 to 485
Converter
5 5
(Disable Echo) PLC
6 6
R
R TX-A A
7 7 S
8 8 S TX-B B 4
2 8
9 9 RX-A
3 5
10 10 2 RX-B
11 11
12 12
Fig. 2. Omni 6000 (3000) Peer-to-Peer Wiring Requirements with PLC

using a Standard RS-232 to RS-485 Converter Module
TB-980401 ALL.70+ 5
RS-485 Wiring Requirements

Multivariable Transmitting The diagram below shows a typical peer-to-peer installation using RS-485
Devices - In addition to the communications, where four flow computers are interconnected in a two-wire,
Serial I/O Module # 68-
6205, the flow computer
multi-drop mode.
must also have an MV
Module to communicate
with multivariable
transmitters. This serial
module is jumpered to IRQ
3 when used in combination
with an MV Module. Without Omni #1 Omni #2 Omni #3 Omni #4
an MV Module, the jumper TB3 TB3 TB3 TB3
is placed at IRQ 2. The MV (TB2) (TB2) (TB2) (TB2)
Module can only be used
with this serial module (68- 1 1 1 1
6205) and is not compatible
2 2 2 2
with the Serial I/O Module #
68-6005. For more 3 3 3 3
information, see Technical
4 4 4 4
Bulletin # TB-980303.
5 5 5 5
6 6 6 6
(B) (B) (B) (B)
7 7 7 7
8 8 8 8
9 9 9 9
10 10 10 10
(A) (A) (A) (A)
11 11 11 11
12 12 12 12
RS-485 Two-wire RS-485 Two-wire RS-485 Two-wire RS-485 Two-wire

Terminated Non-terminated Non-terminated Terminated

RS-485 Two-wire Multi-drop
6 TB-980401 ALL.70+
The peer-to-peer communication link may also be used to transfer data to and
from any other Modbus slave device such as a PLC. The following diagram
shows a typical installation using RS-485 where two flow computers are
connected to a PLC in a two-wire, multi-drop mode.
available at:
(281) 240-6161
the WEB Page at: Omni #1 Omni #2
www.omniflow.com TB3 TB3
or email to: (TB2) (TB2)
techsupport@omniflow.com 1 1
2 2
3 3
4 4
5 5
PLC
6 6
(B) (B) R
7 7 B
S
8 8 A 4
9 9 8
10 10 5
(A) (A)
11 11
12 12
RS-485 Two-wire RS-485 Two-wire

Terminated Non-terminated
Fig. 4. Omni 6000 (3000) Peer-to-Peer Wiring Requirements with PLC

using the RS-485 Two-wire Multi-drop
TB-980401 ALL.70+ 7
Setting up Transactions
To process a transaction the flow computer requires the following data for each
transaction:
Modbus Broadcast Slave ID : The Modbus address of the target device.
Address ‘0’ - This address This can be any valid Modbus address
only applies to write
transactions.
including the broadcast address ‘0’.
Read or Write : Select the appropriate operation.
Source Point Number : Specifies the data base address of the
variable in the source device. For a read
operation the slave is the source. For a write
operation the source is the Omni flow
computer master.
Number of Points : The number of consecutive data variables to
transfer between devices, starting at the
source point number or address.
Destination Point Number : Specifies the data base address of the
variable in the destination device. For a write
operation the slave is the destination. For a
read operation the destination is the Omni
flow computer master.
What Modbus Function Codes Are Used

The flow computer decides what Modbus function code will be used depending
upon the Omni flow computer data type specified in the transaction.
Transactions involving short or long integers or IEEE floats will use Modbus
function codes 03H for reads and 10H for writes. Boolean variables are packed 8
to a byte starting at LS bit and use function codes 01H for reads and 0FH for
writes.
Special Considerations when ‘Modicon

Compatible’ is Selected for Port #2
Some adjustments to the previous entries are needed when communicating with
devices that require ‘Modicon Compatible’ to be selected for the peer-to-peer
port.
1) All data base point addresses (whether source or destination) referring to

the foreign Modicon compatible device, should be entered as one less
than the point address listed. This is needed because the Modicon device
automatically adds one to the address received over the data link and
subtracts one from the address before transmitting. References to data
base point addresses within the Omni flow computer master still use the
normal point address as shown in the Omni documentation.
2) The number of points entry becomes the number of 16 bit registers to

transfer, rather than the number of data variables.
8 TB-980401 ALL.70+
Using Peer-to-Peer with Micro Motion

Coriolis Mass Meters
The Omni flow computer can be configured to accept mass or volume pulses
from a Micro Motion (MM) Coriolis Meter RFT transmitter as well as
communicate via Modbus to the device and obtain variables such as fluid
density and MM transducer alarm status.
The flow computer is equipped with special firmware code to make the interface
to the Micro Motion meter more useful and hopefully simpler. The
communication link between the Micro Motion meter and the flow computer is
via the peer-to-peer link. It is possible to have multiple Micro Motion meters
connected to multiple flow computers as shown below.
Omni #1 Omni #2
TB3 TB3 Micro
(TB2) (TB2) Motion
RFT #2
1 1 R
2 2 S
3 3 27 (Z22) 4
4 4 RS-232 to 485 26 (D22) 8
Converter 5
5 5
(Disable Echo)
6 6 R
R TX-A 27 (Z22)
7 7 S
8 8 S TX-B 26 (D22) 4
2 8
9 9 3 RX-A 5
10 10 2 RX-B
Micro
11 11
Motion
12 12 RFT #1
Note: Termination Points 26 & 27

correspond to the explosion-proof
field-mount RFT9739; and (D22)
& (Z22) to the rack-mount version
of the model.
Fig. 5. Omni 6000 (3000) Peer-to-Peer Wiring Requirements with Micro

Motion RFT Transmitters using a RS-232 to RS-485 Converter
TB-980401 ALL.70+ 9
The following diagram shows a typical peer-to-peer installation using RS-485,

where two flow computers are connected to two Micro Motion RFT9739
transmitters via a proprietary RS-232/485 Serial I/O Module #68-6205.
Micro Motion Elite Model
RFT9739 Transmitter
Connectivity - Both field-
mount (explosion-proof) and
rack-mount models of the
RFT9739 transmitter have
the A and B channels
reversed to the industry Omni #1 Omni #2 Note: Termination resistors
standard applied to Omni
TB3 TB3 may be required with some
flow computers; i.e., the flow
computer’s A channel
(TB2) (TB2) installations.
connects to Micro Motion’s 1 1
B channel. Omni has tested
this connectivity with the 2 2
Micro Motion RFT9739 3 3 Micro Micro
Field-Mount Transmitter, but Motion Motion
connecting to the rack- 4 4 RFT9739 RFT9739
mount version has not yet
been tested. Information on
5 5 #1 #2
this connectivity has been 6 6
(B) (B)
provided by Micro Motion,
Inc. Please contact Micro
7 (B) 7 (B) 26 (D22) 26 (D22)
Motion for further 8 8
@
information.
9 9 120Ω
10 10 (A) (A)
(A) (A)
11 11 27 (Z22) 27 (Z22)
12 12
Note: Termination Points 26 & 27
RS-485 Two-wire RS-485 Two-wire correspond to the explosion-proof
Terminated Non-terminated field-mount RFT9739; and (D22)
& (Z22) to the rack-mount version
of the model.
Fig. 6. Omni 6000 (3000) Peer-to-Peer Wiring Requirements with Micro

Motion RFT9739 Transmitters using the RS-485 Two-wire Multi-
drop.
10 TB-980401 ALL.70+
The Micro Motion Meter is a Modicon Compatible Device

Some adjustments to the peer-to-peer entries are needed when communicating
with devices that require ‘Modicon Compatible’ to be selected for the peer-to-
peer port (Serial Port #2).
1) All data base point addresses (whether source or destination) referring to

the foreign Modicon compatible device, should be entered as one less
than the point address listed. This is needed because the Modicon device
automatically adds one to the address received over the data link and
subtracts one from the address before transmitting. References to data
base point addresses within the Omni flow computer master still use the
normal point address as shown in the Omni documentation.
2) The number of points entry becomes the number of 16 bit registers to

transfer, rather than the number of data variables.
Setting Up the Peer-to-Peer Transactions

Note: Meter Run #1 Density The following peer-to-peer transaction reads the flowing density of the fluid from
I/O point must be assigned the Micro Motion device (Modbus ID #2) and stores it in data base point 7108
to ‘99’ and Serial Port #2
must be assigned to be
(unfactored density, meter run #1).
‘Modicon Compatible’ for
this to work correctly. Note
Transaction #1 Target Slave ID ...…..... 2
also that the MM Modicon
documentation manual lists Read/Write ? ...…..... R
the flowing density as point Source Point # ...…..... 248
number 20249. This is
common with Modicon # of Points ...…..... 2
compatible devices. Where Destination Pnt # ...…..... 7108
there is a 5 digit address,
drop the first digit and
subtract 1 from the point The next transaction reads a 16-bit integer register from the MM meter which
address before using it in a
transaction.
contains packed alarm status bits. These are stored in a special register within
the flow computer which causes them to be time and date tagged, printed and
logged just as though they were flow computer alarms.
Transaction #2 Target Slave ID ...…..... 2

Read/Write ? ...…..... R
Source Point # ...…..... 0
# of Points ...…..... 1
Destination Pnt # ...…..... 3118
The examples above refer to Meter #1 transactions that the flow computer is
requesting. More transactions may be needed depending upon what data is
required and how many meter runs are being used.
TB-980401 ALL.70+ 11
12 TB-980401 ALL.70+
®
Date: 10 01 07 Author(s): KDE.RZD TB # 980402-A
Using the Peer-to-Peer Function in a

Redundant Flow Computer Application
Contents
information contained in RS-232-C Wiring Requirements ........................................................................ 2
User Manual, and is
applicable to all firmware RS-485 Wiring Requirements ............................................................................ 3
revisions Versions .74+.
This is an updated edition of
Setting Up the Peer-to-Peer for Redundant Flow Computer Applications ... 3
the bulletin previously Sensing Failures and Switching between Redundant Computers ................ 5
published under the same
title. Changing the Master / Slave Status via a Modbus Serial Port ....................... 6
Redirecting the Control Signals ........................................................................ 6
Peer-to-Peer Redundancy Sharing Input Signals Between Primary and Secondary Flow Computers .. 7
Schemes - Redundancy
schemes allows for Re-Calibration of Analog Inputs ........................................................................ 7
uninterrupted measurement Sharing Digital I/O Signals Between Primary and Secondary Flow
and control functionality by
interconnecting two Computers ........................................................................................................... 7
identically equipped and Redundant Flow Computer Configuration ....................................................... 8
configured flow computers.
Scope
All firmware revisions Versions .74+ of Omni 6000/Omni 3000 Flow Computers
have the Peer-to-Peer Communications feature, which is available only on
Serial Port #2. This features includes the capability of setting-up redundant flow
computer schemes.
TB-980402  ALL.70+ 1
Abstract
Getting Tech Support - Redundancy involves using two identically equipped flow computers and
Technical support is connecting them in such a way to ensure uninterrupted measurement and
available at:
control functionality in the event of failure of one of the units. This requires that
 (281) 240-6161
all input and output signals are connected to both computers. During normal
Email should be sent via operation, one computer is designated the primary and the other computer the
the WEB Page at:
secondary or backup. To ensure synchronization between both devices,
www.omniflow.com
important variables such as PID controller settings, control valve positions and
or email to:
proving meter factors must be transmitted from the primary flow computer via
Helpdesk@Omniflow.com
the peer-to-peer link to the secondary flow computer. Should a failure of the
primary flow computer occur, the secondary flow computer is automatically
promoted to primary and assumes all control and measurement functions. In
this case the data flow on the peer-to-peer link reverses automatically and the
new master begins to transmit critical data to the slave, assuming that it is
functioning. Peer-to-peer communication errors can occur during the switch over
and are normal. They are cleared by pressing the [Ack] key on the flow
computer keypad or writing to point 1712 (acknowledge station alarms). If the
other flow computer is non-operational, the peer-to-peer communication errors
cannot be cleared.
RS-232-C Wiring Requirements

The following diagram shows the wiring needed when flow computers are
applied in a redundancy scheme via the peer-to-peer feature and using the
proprietary RS-232-C Serial I/O Module Model # 68-6005. They are connected
in a two-wire multi-drop mode.
Omni #1 Omni #2
TB3 TB3
(TB2) (TB2)
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
9 9
10 10
11 11
12 12
Fig. 1. Omni 6000 (3000) Peer-to-Peer Wiring Requirements (RS-232-C

Serial Port)
®
2 TB-980402  ALL.70+
TB-980402 Using the Peer-to-Peer Function in a Redundant Flow Computer Application
RS-485 Wiring Requirements

The diagram below shows the wiring needed when flow computers are applied
in a redundancy scheme via the peer-to-peer feature and using the proprietary
RS-232/485 Serial I/O Module Model # 68-6205. They are connected in a multi-
drop mode using the RS-485 two-wire termination option.
Omni #1 Omni #2
TB3 TB3
(TB2) (TB2)
1 1
2 2
3 3
4 4
5 5
6 6
(B) (B)
7 7
8 8
9 9
10 10
(A) (A)
11 11
12 12
RS-485 Two-wire RS-485 Two-wire

Terminated Terminated

RS-485 Two-wire Termination Mode in a Redundant Flow
Computer Scheme
Setting Up the Peer-to-Peer for Redundant

Flow Computer Applications
The ‘Activate Redundancy Mode’ entry is found in the peer-to-peer setup menu.
Answering ‘Yes’ causes the ‘Next Master’ and ‘Last Master’ entries to disappear
from the menu. They no longer need to be entered as the two flow computers
now manage these two entries automatically. Any data needing to be
synchronized between the flow computers will need to be setup by the user as
transactions in the peer-to-peer menu.
®
TB-980402  ALL.70+ 3
Two transactions are needed to handle redundant PID control:

Transactions #1 & #2 -
Both primary and secondary Transaction #1 Target Slave ID ...…..... 2
flow computers must have
these entries if they will be
Read/Write ? ...…..... W
used for PID control. Source Point # ...…..... 13462
 Transaction #1: Sends NO of Points ...…..... 8
the primary flow
computer PID control Destination Pnt # ...…..... 13470
mode settings
(Auto/Manual, Transaction #2 Target Slave ID ...…..... 2
Local/Remote) to the
secondary flow Read/Write ? ...…..... W
computer. Source Point # ...…..... 7601
 Transaction #2: Sends NO of Points ...…..... 20
the primary flow
computer PID set points Destination Pnt # ...…..... 7601
and valve position values
to the secondary flow
computer. More peer-to-peer transactions are needed if additional data needs to be
transferred, meter factors for example.
Flow computers containing firmware Revisions 22 or 26 handle meter factor
implementation differently than Revisions 20 or 24. These applications maintain
historical meter factor entries which are triggered and stored when the meter
factor is accepted and implemented at the end of a meter proving. As only the
primary flow computer will be doing the actual proving, three special variables
with associated firmware code have been added to the data base of revisions
22 and 26. By writing to and reading from these variables via the peer-to-peer
link, the secondary flow computer can implement the meter factor result
obtained when the primary computer completes and accepts a prove result.
The following two transactions are required:
Transactions #3 & #4
(Applicable to Firmware Transaction #3 Target Slave ID ...…..... 2
Versions 22 & 26 Only) -
Read/Write ? ...…..... W
Both primary and secondary
flow computers must have Source Point # ...…..... 5904
these entries. NO of Points ...…..... 2
 Transaction #3: Used to
send the prove meter Destination Pnt # ...…..... 5904
factor (5904) and the
number of the meter last Transaction #4 Target Slave ID ...…..... 2
proved (5905) to the
secondary flow Read/Write ? ...…..... R
computer. Source Point # ...…..... 5906
 Transaction #4: NO of Points ...…..... 1
Confirms that the meter
factor has been Destination Pnt # ...…..... 5906
implemented in the
secondary flow computer
by reading back a copy
of the number of the
meter run just proved
(5906).
®
4 TB-980402  ALL.70+
Sensing Failures and Switching between

Redundant Computers
Setting Up Peer-to-Peer When ‘Activate Redundancy’ is selected in the peer-to-peer menu, data base
Transactions - For each variables are activated to provide a redundancy switching mechanism which is
transaction, the flow
computer requires the
accomplished by cross connecting 4 digital I/O points from each flow computer
following data (see TB# (primary and secondary).
980401, ‘Peer-to-Peer
Basics’):
These database variables are:
 Target Slave ID: 2863 Watchdog status for this computer. Goes true 5 seconds after
Modbus database
address of target device.
initialization and remains true as long as the flow computer is
 Read/Write?: ‘Read’ (R)
functioning correctly.
selects slave as source 2864 Mastership status for this flow computer. True whenever this flow
device and master as computer is the primary or master computer in the redundancy
destination device.
‘Write” (W) selects scheme.
master as source device 2713 Watchdog status input from the other flow computer. This flow
and slave as destination computer will assume mastership if it sees this point go false.
device.
 Source Point #: 2714 Mastership status input from the other flow computer. This flow
Specifies database computer will relinquish mastership if it sees this point go true.
address (or first address
in sequence) of data to
transfer from source to
destination device.
O
 N of Points: Total
number of consecutive
database addresses in
sequence to transfer.
 Destination Point #: Omni #1 Omni #2
Specifies database TB1 TB1
address (or first address 1 1
in sequence) in
2 2
destination device of
data received from 3 3
source device. 4 4
5 5
6 6
Redundancy Failover
Wiring - Any 4 digital I/O 7 7
points may be used to 8 8

Other Master Status (2714) Others Master Status (2714)
provide a failover switching 9 9
mechanism. Fig. III.8-3 is an Master Status (2864) Master Status (2864)
10 10
example that shows digital Others Watchdog (2713) Others Watchdog (2713)
I/O 9 through 12 being used 11 11
Watchdog Out (2863) Watchdog Out (2863)
12 12
TB11 TB11
+ +
- -
Fig. 3. Omni 6000 / 3000 Redundancy Failover Wiring
®
TB-980402  ALL.70+ 5
Changing the Master / Slave Status via a

Modbus Serial Port
Sometimes it may be necessary to force a swap of primary (master) and
Technical support is secondary (slave) flow computers. For example, if both primary and secondary
available at: flow computers are functioning correctly (i.e. watchdogs are OK) but the MMI
 (281) 240-6161 serial communication link to the primary flow computer was lost, it would be
Email should be sent via necessary to make the secondary flow computer the primary. Two special data
the WEB Page at: base points are available to provide this function, they are:
www.omniflow.com
2715 Be Master - writing a one to this point automatically promotes this
or email to:
helpdesk@omniflow.com
flow computer to master. This in turn causes the digital I/O point
which is assigned point 2864 ( Mastership Status ) to go true.
Assuming the digital I/O are cross connected as shown in the
preceding figure, the other flow computer will automatically relinquish
mastership when this happens.
Note: The 2716 command 2716 Be Slave - writing a one to this point automatically demotes this flow
will not work if the other flow computer to slave. This in turn causes the digital I/O point which is
computer’s watchdog status assigned point 2864 ( Mastership Status ) to go false. Assuming the
is not active (i.e., the other digital I/O are cross connected as shown in the preceding figure, the
computer must be
functioning correctly before other flow computer will automatically assume mastership when this
this flow computer can give happens.
up mastership).
Both the above commands are edge triggered needing only to be turned on,
they do not need to be turned off.
Redirecting the Control Signals

In the event of a primary/secondary flow computer swap, a method is needed to
redirect the appropriate 4-20 mA signals to control valves and other functions.
One way of doing this is to use a DC relay with type C contacts. Suitable relays
are available with multiple sets of contacts. The relay can be energized by the
digital output assigned to indicate ‘Mastership Status’ from one of the flow
computers.
®
6 TB-980402  ALL.70+
Sharing Input Signals Between Primary and

Secondary Flow Computers
In a redundant system all input signals must be connected to both primary and
secondary flow computers. Voltage pulse signals such as flowmeters and
densitometer devices must be connected in parallel to the appropriate inputs of
both flow primary and secondary computers. Current pulse signals must first be
converted to voltage pulses by suitable input shunt resistor or source resistor.
As a general rule, follow the wiring recommendations shown for a normal single
flow computer installation (see Volume 1 of the User Manual) and then simply
wire the second flow computer terminals in parallel with the first computer.
Analog 4-20 mA signals should be converted to 1-5 volt signals by using a low
temperature coefficient precision 250 ohm resistor. For each signal, configure
the combo modules of both flow computers for 1-5 volt inputs and wire them in
parallel across an appropriate 250 ohm resistor mounted externally to the flow
computers.
Re-Calibration of Analog Inputs

Each flow computer input channel which is configured for 1 - 5 volt input signals
will need to be verified for accuracy. Re-calibration may be necessary
depending upon the accuracy of the 250 ohm resistor used and how well it
matches the internal 250 ohm resistor that was used when the input channel
was originally calibrated. The system wiring between the flow computer and the
250 ohm resistor can also slightly affect the input calibration.
Sharing Digital I/O Signals Between Primary

and Secondary Flow Computers
Digital I/O channels configured as status inputs should be simply wired in
parallel (ORed) with the other flow computer. Digital I/O channels configured as
outputs may possibly require relay isolation similar to that needed for analog
outputs described previously. Typical output signals that need to be relay
isolated are sampler pulse outputs. Prover control signals do not usually need
to be relay isolated as the secondary computer will never be attempting to
control the prover while it is the slave or secondary computer. The user will
need to determine which outputs need to be isolated based on whether it is
possible or likely that the slave computer would activate the output when not in
control.
®
TB-980402  ALL.70+ 7
Redundant Flow Computer Configuration

Defining which Computer will be the Master or Primary
Computer at Power Up*
When using flow computers in the redundant pair configuration (Master and
Slave) it is usual to designate one flow computer as the preferred primary unit
when power is applied to both flow computers simultaneously.
This is achieved by adding the following two Boolean Statements, into the flow
computer designated as the Secondary or Back-Up computer. Any two
statements can be used; however the example below uses statements 1080
and 1081. If other statement numbers are used make sure that the 1080
number in the second statement matches the number of the first statement.
1080: 2864&2714&/2863 Rmk: MasterConflict? Check for master conflict

at power-up time
1081: 2716=2716+1080 Rmk: If so make Slave If I’m master, switch to
slave status
*Note: When power is applied simultaneously to both flow computers in a

redundant pair, both will attempt to assume mastership with uncertain results.
®
8 TB-980402  ALL.70+
Communicating with Honeywell SMV3000

Multivariable Transmitters
Contents
information contained in the DE Protocol Overview ........................................................................................ 2
User Manual, and is
revisions .72+.
The Honeywell Handheld Communicator...................................................... 3
Combo Module LED Status Indicators ............................................................. 3
Communication with
Honeywell SMV3000 Switching Between Analog and Digital Mode.................................................. 3
Smart Transmitters - This
feature allows you to
Viewing the Status of the Honeywell Transmitter from the Keypad ............. 4
communicate with Viewing the Status of the Honeywell Transmitter from the Keypad .......... 5
Honeywell SMV3000 Smart
Multivariable Transmitters Obtaining More Detailed Status Information from the Keypad...................... 8
which provide Differential
Pressure , Temperature and Transducer Alarms Logged by the Flow Computer...................................... 12
Static Pressure, via Omni’s HV Combo Module Address Jumpers ............................................................ 13
HV type Process I/O Combo
Modules and using How the I/O Points are Assigned .................................................................... 14
OmniCom Revision........................................................................................... 15

available at:
(281) 240-6161 Scope
the WEB Page at: All firmware revisions of Omni 6000/Omni 3000 Flow Computers containing
www.omniflow.com firmware 21.72+, 23.72+, 27.72+ are able to communicate with Honeywell
or email to: SMV3000 Smart Multivariable Transmitters. This feature uses Honeywell’s DE
techsupport@omniflow.com Protocol and requires that an HV Combo I/O Module be installed in your flow
computer.
TB-980502 21/23/27.72+ 1
Abstract
Using an ‘HV’ Combo I/O Module, the Omni Flow Computer can communicate
with up to 4 Honeywell SMV3000 Smart Multivariable transmitters. These
transmitters provide Differential Pressure, Temperature and Pressure signals
using Honeywell’s DE Protocol. Only one ‘HV’ Type Combo Module can be
installed in the flow computer. Loop power is provided by the ‘HV’ combo
module.
DE Protocol Overview
Digital data is transmitted serially between the flow computer and Honeywell
Smart Transmitters by modulating the current in the two wire loop connecting
is transmitted at 218.47 bits per second with a digital ‘0’ = 20 mA and a digital ‘1’
= 4 mA.
In normal operation, the Honeywell transmitter operates in the ‘6-byte Burst
Mode’. In this mode, the transmitter transmits the following data to the flow
computer every 366 msec:
Byte #5 Database ID (indicates where in the transmitters database Byte #6
below belongs)
maintains an exact copy of the multivariable transmitters configuration database.
The transmitter database which is sent to the Omni flow computer is about 132
bytes. Based on the burst rate of the transmitter it can take about 45 to 55
seconds to completely build a copy of the transmitter database within the flow
computer. The transmitter database is continuously compared against the flow
computer configuration settings for that transmitter. The flow computer
2 TB-980502 21/23/27.72+
TB-980502 Communicating with Honeywell SMV3000 Multivariable Transmitters
The Honeywell Handheld Communicator

transmitter:
(1) Lower Range Value or Zero
(2) Transmitter Span or Max Range
(3) Damping Factor
(4) Tag Name
(5) DP, SP and Temperature conformance bits
Any changes made to 1, 2, 3 and 5 using the handheld communicator will be
overwritten by the flow computer. In the digital mode it is not absolutely
necessary to calibrate the transmitters outputs using the handheld
communicator. The user can however trim the transmitters output calibration
using the handheld communicator if he so desires without interference from the
flow computer (see Honeywell documentation for details of trimming corrects).
Whether the transmitter is trimmed with the handheld or not, the digital signals
should be final calibrated ‘end to end’ using the normal analog input method
described in Chapter 8 of Volume 1.

Each I/O channel of the ‘HV’ Combo module has a set of two LED indicators,
one green and one red. The green LED shows all communication activity taking
transmitter.

Connecting an analog mode Honeywell multivariable transmitter to the computer
will cause the flow computer to automatically switch the transmitter to the digital
DE mode sending out a series of ‘Wake up commands’ to the Honeywell
transmitter. A switch over to the digital mode by the transmitter will cause the
green LED on the combo module to pulse steadily indicating that
communications have been established.
To disable the wake up command and initialize communications between the
Honeywell transmitter and the flow computer, delete all I/O point assignments
within the flow computer to that I/O point. Using the Honeywell handheld
communicator press [Shift] [A/D] and wait till the handheld displays ‘Change to
Analog?’ Answer by pressing [Enter] (Yes). ‘SFC Working’ will be displayed.
The green LED on the ‘HV’ Combo module on that channel will stop pulsing. Re-
entering the I/O point will cause the Omni to send the wake up command to the
Honeywell and after three command sends the green LED on the Honeywell
module will pulse at a steady 3Hz rate.
TB-980502 21/23/27.72+ 3
Viewing the Status of the Honeywell

Transmitter from the Keypad
To verify the data being received from the smart transmitter, press [Input]
[Status] and [Enter] from the front panel. The following data displays:
HV-1 Transmitter
DB Status
OK
Gstatus NON-
CRITICAL
DP%
25.00
SP%
76.50
TT%
32.13
DP LRV
0.0
DP Span
400.0
DP Damp Secs.
.16
DP Conformity bit
0
SP LRV
406.8
SP Span
27680.2
SP Damp Secs
.16
SP Conformity bit
0
TT LRV
.0
TT Span
100.0
TT Damp Secs
.3
TT Conformity bit
0
SW Revision
2.1
Serial #
xxxxxxxxxx
DP Range
400.0
SP Range
20760.5
TT Range
850.0
ID/TAG SMV-
3000
Filter Hertz
60
SensorType RTD-
PT100
4 TB-980502 21/23/27.72+

HV-1 Transmitter : Indicates the Honeywell Multivariable Combo Module
(HV) and the channel number on that module. As there
can be only one HV module installed, this number can
only be 1 through 4.
DB Status : There are five status states.
transducer.
30-45 sec or so.
Burst Mode. Because the flow computer
will not tolerate this mode of operation, this
status display should only be displayed
momentarily as the flow computer will
automatically switch the transmitter into
the 6-Byte Burst Mode.
TB-980502 21/23/27.72+ 5
Gstatus : Gross Status Flag value:

1) OK : No errors are reported by the SMV
transmitter.
2) Critical Critical error reported by the SMV
transmitter.
3) Non-Critical : An error of a non critical nature has been
reported by the SMV transmitter.
4) Reserved : Consult Honeywell if this status value is
returned.
DP% : Differential pressure variable value in percentage of the
transmitter span. A -25.00 could mean that the
transmitter is not communicating (see Status definition
previous).
SP% : Static pressure variable value in percentage of the
previous).
TT% : Temperature variable value in percentage of the
previous).
DP LRV : Lower Range Value of the DP variable in engineering
units. Engineering units are inches of water at 39
degrees Fahrenheit.
DP Span : The Span of the Differential pressure variable in
engineering units (the span is the difference between the
lower and upper ranges of the transmitter). Engineering
units are inches of water at 39 degrees Fahrenheit. The
flow computer will display ‘DB Error’ if the user tries to
enter a span of 0% or a span which would exceed the DP
sensor ‘range’ (described later).
DP Damp Secs : Damping Time of the DP transmitter output in seconds.
DP Conformity Bit : Meaningful only with differential pressure transmitters.

square root output. The flow computer requires linear
output and will automatically set this bit to 0 should it be
set to a 1.
SP LRV : Lower Range Value of the Static Pressure variable in
engineering units. Engineering units are inches of water
at 39 degrees Fahrenheit.
SP Span : The Span of the Static Pressure variable in engineering
units (the span is the difference between the lower and
upper ranges of the transmitter). Engineering units are
inches of water at 39 degrees Fahrenheit. The flow
computer will display ‘DB Error’ if the user tries to enter a
span of 0% or a span which would exceed the static
pressure sensor ‘range’ (described later).
6 TB-980502 21/23/27.72+
SP Damp Secs : Damping Time of the Static Pressure transmitter output in

seconds.
SP Conformity Bit : Meaningful only with differential pressure transmitters.
TT LRV : Lower Range Value of the temperature variable in
engineering units. Engineering units are degrees Celsius.
TT Span : The Span of the Temperature variable in engineering
degrees Celsius. The flow computer will display ‘DB
Error’ if the user tries to enter a span of 0% or a span
which would exceed the temperature sensor ‘range’
(described later).
TT Damp Secs : Damping Time of the Temperature transmitter output in
seconds.
TT Conformity Bit : Meaningful only with differential pressure transmitters.

Software Revision : Current Software installed within the smart multivariable
device.
Serial # : Serial Number of the smart multivariable device.
DP Range : Maximum range of the DP sensor in inches of water at 39
degrees Fahrenheit. The transmitter will not accept
configuration entries which exceed this value.
SP Range : Maximum range of the Static Pressure sensor in inches
of water at 39 degrees Fahrenheit. The transmitter will
not accept configuration entries which exceed this value.
TT Range : Maximum range of the Temperature sensor in degrees
Celsius. The transmitter will not accept configuration
entries which exceed this value.
ID/TAG : ASCII string used to identify the SMV DP transmitter.
Filter Hertz : Frequency used to filter sensor signals to minimize AC
mains interference. Selections are 50 or 60 Hertz.
Sensor Type : Temperature sensor types are:
1) RTD-PT100
2) J type Thermocouple
3) K type Thermocouple
4) T type Thermocouple
5) E type Thermocouple
Note: Thermocouples can be internally or externally
compensated.
TB-980502 21/23/27.72+ 7
Obtaining More Detailed Status Information

from the Keypad
Additional data based upon the ‘Primary’, ‘Secondary’ and ‘Tertiary’ ‘Detailed
Status’ bytes which are retrieved from the SMV data base is available by
pressing [Input] [Status] [Alarm] and [Enter]. The display will approximate the
following messages depending upon certain bits being ON in the appropriate
‘detailed status byte’. Some of these status bits also cause alarm status points
within the flow computer data base to be activated. When this happens, these
alarm events are time and date tagged and logged in the alarm log as any other
flow computer alarm.
HONEYWELL OMNI
DETAILED STATUS ALARM
TEXT IN ‘BOLD’ DISPLAYED
BYTE-BIT POINT(S)
ACTIVATED
Meter Body Fault: Communication between 2n44 CR
1-0 sensor board and SMV main board 2n47 CR
electronics is suspect. 2n50 CR
1-1 Characterization PROM Fault or Checksum 2n44 CR
Error 2n47 CR
1-2 Suspect Input: Possibly Meter Body or 2n44 CR
Electronics Failure 2n47 CR
1-3 DAC Compensation: Fault Detected 2n52 CR
1-4 NVM Fault: Non Volatile Memory Error 2n52 CR

Detected
1-5 RAM Fault: RAM Memory Error Detected 2n52 CR
1-6 ROM Fault: ROM Memory Error Detected 2n52 CR
2n44 CR
1-7 PAC Fault Detected
2n47 CR
2-0 MB OverTemp: Meter Body Sensor Over 2n51 NC
Temperature
2-1 DP Zero Correction Value is Outside of 2n42 NC
Acceptable Limits
2-2 DP Span Correction Value is Outside of 2n42 NC
Acceptable Limits
Status 2-3 (Consult with Honeywell for
2-3 
meaning)
2-4 MB Overload or : (Always with next 2n47 CR
message)
NC = None Critical Alarm. CR = Critical Alarm Override Action Considered.
Note: The ‘n’ in the Modbus address refers to the number of the meter run.
8 TB-980502 21/23/27.72+
HONEYWELL OMNI
BYTE-BIT POINT(S)
ACTIVATED
2-5 Meter Body Fault: Pressure input is twice 2n47 CR
the URL
DP Cal Corr Default: ‘Reset Corrects’
2-6 command issued or ‘Calibrate and Power 2n42 NC
Cycle’ performed
2-7 DAC Tempco Data Bad: Analog mode only. 
2n44 CR
Invalid Database: Some error detected in
3-0 2n47 CR
the SMVs configuration. All PVs are suspect.
2n50 CR
3-1 Suspect SP Input: Static pressure input 2n47 CR
suspect
3-2 
meaning)
3-3 
meaning)
3-4 DP Term Out of Range 
V-T Term Out of Rng: Viscosity temperature
3-5 
term out of range
D-T Term Out of Rng: Density temperature
3-6 
term out of range
Ind Var Out of Range: Independent variable
3.7 
out of range
4-0 
meaning)
4-1 Excess Zero Corr SP: Excess zero 2n45 NC
correction for static pressure
4-2 Excess Span Corr SP: Excess span 2n45 NC
SP is Absolute: Static pressure sensor is
4-3 
absolute
SP is Gauge: Static pressure sensor is
4-4 
gauge
4-5 
meaning)
4-6 SP Corrects Reset: Static pressure 2n45 NC
corrections reset
TB-980502 21/23/27.72+ 9
HONEYWELL OMNI
BYTE-BIT POINT(S)
ACTIVATED
4-7 
meaning)
5-0 
meaning)
5-1 
meaning)
5-2 
meaning)
5-3 
meaning)
5-4 DP in Input Mode 2n43 CR
5-5 SP in Input Mode 2n46 CR
5-6 Temp in Input Mode 2n49 CR
5-7 PV4 in Input Mode 
6-0 2 Wire RTD Used 
6-3 2 Wire TC Used 
6-4 DP in Output Mode 2n43 CR
6-5 SP in Output Mode 2n46 CR
6-6 Temp in Output Mode 2n49 CR
6-7 PV4 in Output Mode 
7-0 Temp A/D Fault : Temperature A to D failure 2n50 CR
7-1 Temp Char Fault: Temperature 2n50 CR

characterization fault
7-2 Temp Input Suspect: Temperature input 2n50 CR
signal is suspect
7-3 
meaning)
7-4 Temp NVM Fault: Temperature non-volatile 2n50 CR
memory fault detected
7-5 
meaning)
10 TB-980502 21/23/27.72+
HONEYWELL OMNI
BYTE-BIT POINT(S)
ACTIVATED
7-6 
meaning)
7-7 
meaning)
Delta Temperature : (FUTURE - Consult
8-0 
with Honeywell for meaning)
8-1 Excess Zero Cor Temp 2n48 NC
8-2 Excess Span Cor Temp 2n48 NC
8-3 Temp Input Open : Open circuit 2n50 CR

temperature sensor
8-4 Temp Over Range : Process temperature is 2n50 CR
over range
Redun Backup Temp : (FUTURE - Consult
8-5 
8-6 Temp Corrects Active 2n48 NC
8-7 Temp Sensor Mismatch 2n50 CR
TB-980502 21/23/27.72+ 11
Transducer Alarms Logged by the Flow

Computer
The following alarm points are automatically updated with data contained in the
‘detailed status’ bytes within the flow computers copy of the SMVs data base
(see the previous table). These alarms are time and date tagged and logged by
the flow computer whenever the respective bit changes state. Other than the
logging function, non critical alarms cause no other action to occur. Critical
alarms are alarms which are considered to adversely impact the credibility of the
measurement reading, these alarms cause the flow computer to examine the
‘Override Code’ strategy and apply an override if so configured.
ADDRESS OF ALARM TITLE ALARM TYPE

ALARM POINT
2n42 Meter ‘n’ DP: Invalid Corrects or Corrects NC
Reset
2n43 Meter ‘n’ DP is in the Input or Output Mode CR
2n44 Meter ‘n’ DP Signal is Suspect CR
2n45 Meter ‘n’ Pressure: Invalid Corrects or Corrects NC

Reset
2n46 Meter ‘n’ Pressure is in the Input or Output CR
Mode
2n47 Meter ‘n’ Pressure Signal is Suspect CR
2n48 Meter ‘n’ Temperature - Invalid Corrects or NC

Corrects Reset
2n49 Meter ‘n’ Temperature is in the Input or Output CR
Mode
2n50 Meter ‘n’ Temperature Signal is Suspect CR
2n51 Meter ‘n’ Body Fault - Over Temperature NC
2n52 Meter ‘n’ Critical Failure of SMV Electronics CR
2n53 Meter ‘n’ SMV Not Communicating CR
12 TB-980502 21/23/27.72+
HV Combo Module Address Jumpers

The HV Combo Module actually uses the same physical PCB module as a
regular H type combo module, except it uses a different address jumper setting.
Module Address
Jumpers
In ‘*’ Position
Green LED
Indicates Any
Activity
* * *
Red LED Indicates

OMNI is
Transmitting
SMV Channel #1
SMV Channel #2
Transmitter Loop
Status LEDs
SMV Channel #3
SMV Channel #4
Figure 1. Setting the Address Jumpers of the HV Combo Module
TB-980502 21/23/27.72+ 13
How the I/O Points are Assigned

When the flow computer detects that an ‘HV’ combo module is installed it
automatically allocates 12 of its 24 process inputs to the ‘HV’ module. The
presence or absence of combo modules is checked after a RESET ALL RAM or
after a CHECK I/O MODULES command is executed.
Although the ‘HV’ combo has only 4 physical Honeywell DE ports, each SMV-
3000 provides 3 variables for a total I/O requirement of 4 x 3 = 12. As the total
process input count of the flow computer is limited to 24 it is obvious that if an
‘HV’ combo module is fitted there can only be 3 other combo modules of type A,
B, E/D, E or H. The ‘HV’ combo module is always the last module in the list,
and the I/O assignments reflect this fact (see the following example).
Example 1: Omni 6000 - 2A - H1 – HV ( Flow computer contains - 2 ‘A’

combos, 1 ‘H’ combo, and an ‘HV’ combo).
st
The 1 ‘A’ combo is allocated: Input points 1, 2, 3 & 4
Output points 1&2
nd
Output points 3&4
The ‘H’ combo is allocated: Input points 9, 10, 11 & 12

Output points 5&6
The ‘HV’ combo is allocated: Input points 13, 14, 15 & 16 Diff. Pressure
17, 18, 19 & 20 Temperature
21, 22, 23 & 24 Pressure
Output points 7&8
While the example shown above employs 4 combo modules in total, it uses all
24 process input assignments, this means that 2 physical I/O module slots will
be unusable on the backplane.
To configure an ‘HV’ combo module it is only necessary to configure the
Diff-Pressure I/O points in the Meter Run Config menu, the I/O points for the
temperature and pressure variables are automatically assigned by the flow
computer and cannot be changed by the user.
14 TB-980502 21/23/27.72+
Using the above example the following table identifies the I/O point assignments
that will occur.
available at: DIFFERENTIAL
TEMPERATURE PRESSURE
(281) 240-6161 PRESSURE
the WEB Page at: METER RUN # 1 13 17 21
www.omniflow.com
METER RUN # 2 14 18 22
or email to:
techsupport@omniflow.com METER RUN # 3 15 19 23
METER RUN # 4 16 20 24
Numbers in bold are entered by the user. Numbers in italics are assigned
automatically by the flow computer and cannot be changed.
OmniCom Revision
OmniCom revision ??.72 or later is required to support the SMV-3000
multivariable transmitter.
TB-980502 21/23/27.72+ 15
16 TB-980502 21/23/27.72+
Rosemount 3095FB Multivariable Sensor

Interface Issues
Contents
information contained in Important Omni Flow Computer Compatibility Issues When Using SV
User Manual, applicable to
Firmware Revision
Combo Modules .................................................................................................. 3
21.72+/25.72+ and Serial Communication Module Compatibility ................................................................. 3
23/72.+/27.72+. Other Known System Incompatibilities .......................................................................... 3
Equipment Ordering Limitations .................................................................................... 3
Connectivity Issues When Connecting to the 3095FB Multivariable
Transmitters: Multi-drop versus Point-to-Point............................................... 4
Advantages of Multi-drop Configurations....................................................................... 4
Disadvantages of Multi-drop Configurations.................................................................. 4
Jumper Settings for the Omni SV Combo Module .......................................... 5
Setting the Address of the SV Combo Module .............................................................. 6
Setting the Termination Jumpers for the Each of the SV RS-485 Ports ........................ 6
Initial Setup of the Rosemount 3095FB Multi Variable Transmitter ........... 8
Connecting the 3095FB to the Omni Flow Computer ..................................... 9
3095FB Transmitter RS-485 Connections................................................................... 10
3095FB Transmitter Power Connections and Requirements....................................... 10
Isolation and Transient Protection Issues.................................................................... 11
Wiring Considerations When Replacing a Multi-dropped 3095FB Transmitter............ 11
Configuring the Omni Flow Computer to use the 3095FB Multi Variable
Transmitter ........................................................................................................ 12
Configuring the Meter Run I/O..................................................................................... 12
Selecting the Device Type ........................................................................................................ 12
Selecting the SV Combo Module Port ...................................................................................... 12
Select Modbus Address for 3095FB ......................................................................................... 12
What I/O Points are Used and Why .......................................................................................... 12
DP, Pressure and Temperature Setup Entries Needed............................................... 14
Data Transferred between the 3095FB Transmitter and the Omni Flow
Computer ........................................................................................................... 14
Polling Intervals for Process Variables and Critical Alarms ......................................... 15
Critical 3095FB Alarms Monitored By The Flow Computer ......................................... 15
Synchronizing the 3095FB and the Flow Computer Configurations........... 16
TB-980501 21/25.72+ & 23/27.72+ 1

Viewing the 3095FB Data at the Flow Computer Front Panel ...................... 16
Installing, Replacing and Calibrating 3095FB Transmitters......................... 17
Wiring Issues ............................................................................................................... 17
Using the Omni Flow Computer to Set the Modbus Address of the 3095FB ............... 19
Using a Laptop PC to Trim the 3095FB Calibration ..................................................... 20
Scope
Firmware Revisions 21.72+/25.72+ and 23.72+/27.72+ of Omni 6000/Omni
3000 Flow Computers are affected by the issues contained in this technical
bulletin. This Bulletin applies to Orifice/Differential Pressure Liquid Flow
Metering Systems and to Orifice Gas Flow Metering Systems.
Abstract
Getting Tech Support - The Rosemount 3095FB Multivariable sensor assembly is used to measure
Technical support is differential pressure (DP), static pressure (SP) and line temperature (T).
available at:
Application of the 3095FB is limited to flow computer revisions 21, 23, 25 and
(281) 240-6161
27 which work with differential head devices such as orifice meters, nozzles and
Email should be sent via venturi meters. Because the flow computer is limited to a maximum of four
the WEB Page at:
meter runs it is also limited to a maximum of four 3095FB multivariable
www.omniflow.com
transmitters.
or email to:
techsupport@omniflow.com Data is accessed from the 3095FB transmitter via a 2 wire RS-485 data link at
9600 baud using Modbus protocol. Technically, it would have been possible to
use one of the flow computer’s standard serial ports to communicate with the
3095FB but this would have caused several problems:
❑ Reduced the number of serial ports available for use with SCADA, PLCs
and OmniCom etc.
❑ Extra 'A’ type combo modules would have to be purchased simply to
provide analog outputs in a minimum system requiring just the
multivariables.
Omni chose to design a special ‘SV’ combo module which includes two 2 wire
RS-485 ports and six 4-20 mA analog outputs. With this module it becomes
possible to provide a powerful Omni 3000 system with the following specs:
❑ Four meter runs with Differential Pressure, Static Pressure and
Temperature inputs.
❑ Four communication ports for SCADA, PLC, Printer, OmniCom etc.
❑ Twelve Digital I/O for logic control
❑ Six digital to analog outputs.
This SV module is capable of connecting to one to four 3095FBs in various
multi-drop configurations. A second SV combo module can be utilized in
applications where point to point operation of more than two multivariable
transmitters is desirable.
2 TB-980501 21/25.72+ & 23/27.72+

TB-980501 Rosemount 3095FB Multivariable Sensor Interface Issues
Important Omni Flow Computer Compatibility

Issues When Using SV Combo Modules
The ‘SV’ combo modules are effectively serial I/O modules which have been
specially designed to communicate with various multivariable transmitters.
Changes have been made to the IRQ priorities to accommodate these ‘SV’
combo modules. These IRQ changes also involve the ‘Serial I/O Combo
Modules’ that are used to connect to printers, OmniCom, PLCs and SCADA
devices.
Serial Communication Module Compatibility

‘SV’ combo modules cannot be installed in flow computer systems containing
RS-232-C Serial I/O Combo modules model type 68-6005. The IRQ settings on
the 68-6005 serial combo module are not jumper selectable and are
incompatible with the 'SV’ combo modules. The flow computer will not be able to
initialize or boot up if this module is installed (this will be evident by a blank LCD
screen which flashes its backlighting on and off every 1.5 seconds).
The more recent 68-6205 serial module which is both RS-232-C and RS-485
compatible, has jumper selectable IRQ settings, these must be installed in the
‘IRQ 3’ position when an ‘SV’ combo module is present (see technical bulletin
TB-980503 for more details).
Other Known System Incompatibilities

At the time this bulletin was prepared, it was not possible to install both an ‘SV’
combo module and an ‘HV’ (Honeywell multivariable) combo module.
Equipment Ordering Limitations

Because of the compatibility issues raised in the above paragraphs, it is not
possible for the customer to retrofit existing flow computer installations with ‘SV’
combo modules. Any system which requires ‘SV’ combo modules, must be
purchased new from Omni, or the system must be returned to Omni to be
modified (contact a sales person at Omni for upgrade details and pricing).
TB-980501 21/25.72+ & 23/27.72+ 3

Connectivity Issues When Connecting to the

3095FB Multivariable Transmitters: Multi-drop
versus Point-to-Point
The 3095 FB multivariable transmitter is a four wire device, two power wires and
two wires for the RS-485 serial communication link. It can be connected in a
‘point-to-point’ or ‘multi-drop’ wiring configuration.
Advantages of Multi-drop Configurations

The advantages of multi-drop configurations are:
❑ Possibly less wire may be needed to connect devices under certain
conditions. This may or may not be the case depending upon
equipment placement.
❑ One Omni SV Combo module can handle up to four 3095 FB
multivariable transmitters. An Omni 3000 can be used in place of an
Omni 6000 and handle four meter runs.
Disadvantages of Multi-drop Configurations

Disadvantages of multi-drop configurations are:
❑ Multiple Modbus IDs required. Each multi-dropped transmitter must
have a unique Modbus ID which matches the Modbus ID selected within
the flow computer for that meter run multivariable.
❑ Possibility of errors when replacing multivariable transmitters.
Because of the multiple Modbus addresses it is not possible to simply
take a transmitter off the shelf and install it in a multi-drop configuration.
This is because transmitters come from Rosemount with the Modbus
address defaulted to ‘1’ and there may already be a transmitter in the loop
using that address. Adding a second transmitter with the same address
as an existing transmitter would effectively cause a loss of signal on both
transmitters (existing and new). Depending upon where the transmitter is
in the wiring, ‘termination’ jumpers may or may not be required on the
replacement transmitter (see below).
❑ Transmitter interaction is possible. While not likely, a hardware failure
in one transmitter could compromise the integrity of the shared RS-485
link causing a loss of flow signals for all meter runs. Calibrating a
transmitter via a laptop computer requires the wiring to be disturbed, care
must be taken not to disconnect other transmitters in the same multi-drop
loop.
4 TB-980501 21/25.72+ & 23/27.72+

❑ RS-485 termination requirements more complex. RS-485 transmission

wires must have only one beginning and one end (they cannot be used in
a ‘star’ configuration). Both ends of the wire must be terminated, meaning
only two devices in the loop need terminating. In a point-to-point
configuration, this simply means both the flow computer and transmitter
are terminated. In a multi-drop configuration, the user must ensure that
only the end devices have the termination jumpers in. This means that
some transmitters may have the terminating jumpers in while others may
have them out. Remember that the Omni may or may not be at the end of
the wire so it may or may not be one of the terminated devices.
❑ Process variable update time may exceed the flow computers 500
msec cycle time. Critical measurement or control systems require that
the process variables be input to the flow computer as fast as possible for
best performance.
Jumper Settings for the Omni SV Combo

Module
The Multi Variable ‘SV’ Combo module contains several sets of jumpers which
must be installed correctly (see figure below).
Port 1 (3) Port 2 (4)

Tx/RTS Leds Red Tx/RTS Leds Red
Recv Led Grn Recv Led Grn
RTS GND
T T
SV RS-485 Termination Jum p ers E E
R R SV Port 1 ( 3 )
Both Jm pers In = Port Terminated M M
Both Jm pers Out = Port Non-Terminated
Alway s RTS RTS GND

T T
E E
SV Address Jum p er R R SV Port 2 ( 4 )
Jm p In = 1st SV Combo M M
Jm p Out = 2nd SV Combo
Port Numbers in ( ) are for 2nd SV Module

A lway s IRQ 2 BRD SEL
2 4 IRQ
Fig. 1. Omni Model 68-6203 Multivariable Interface Module - SV Combo

Module
TB-980501 21/25.72+ & 23/27.72+ 5

Setting the Address of the SV Combo Module

The flow computer can accept up to two ‘SV’ Combo modules, each with a
unique address determined by the ‘BRD SEL’ jumper shown in Figure 1. With
this jumper fitted the flow computer will report that a ‘SV1’ module is installed
and SV ports 1 and 2 will be available. Without this jumper in the ‘BRD SEL’
position the flow computer will report that a ‘SV2’ module is installed and SV
ports 3 and 4 will be available. Note that a system can have a ‘SV2’ module
without a ‘SV1’ being installed, in this case only SV ports 3 and 4 would be
available.
Setting the Termination Jumpers for the Each of the SV

RS-485 Ports
Multivariable RS-485 communication circuits must have two ends only, a ‘star’
configuration with more than two ends or a ‘loop’ configuration with no
ends is not allowed. The devices at both ends of the circuit must be jumpered
to provide termination.
3095 FB 3095 FB 3095 FB 3095 FB

MV MV MV MV
ID #1 ID #2 ID #3 ID #4
Omni
Flow
Computer
This Device This Device
Must Be Must Be
Fig. 2. Multi-drop Configuration with Flow Computer Terminated
Both jumpers marked ‘TERM’ must be installed to terminate a flow computer

‘SV’ port (see Fig. 1 previous page). Termination settings for the 3095FB are
shown later in this document.
3095 FB This Device 3095 FB

MV Must Be MV
ID #1 Terminated ID #4
Omni
Flow
Computer
This Device
Must Be
3095 FB 3095 FB
MV MV
Terminated
ID #2 ID #3
Fig. 3. Multi-drop Configuration with Flow Computer Non-terminated
6 TB-980501 21/25.72+ & 23/27.72+

3095 FB 3095 FB 3095 FB 3095 FB

MV MV MV MV
ID #1 ID #2 ID #3 ID #4
Omni
Flow
Computer
Star Configuration Not Allowed!
Fig. 4. Unacceptable Configuration - Five Termination Points
All 4 MV Ports of 3095 FB 3095 FB 3095 FB 3095 FB

Flow Computer MV MV MV MV
Must Be Terminated ID #1 ID #1 ID #1 ID #1
Omni
Flow
Computer
Using
Independent
MV Ports Modbus IDs of 3095FBs All Four 3095FB
Can Be The Same In This Transmitters
Point to Point Configuration Must Be Terminated
Fig. 5. Point-to-Point Wiring Configuration
In the point-to-point configuration each 3095FB transmitter is connected to an

independent ‘SV’ port of the flow computer. Because each ‘SV’ port is now
connected to only one 3095FB, each 3095FB can now use the default Modbus
address ‘1’, greatly simplifying transmitter replacement issues discussed later in
this document.
TB-980501 21/25.72+ & 23/27.72+ 7

Initial Setup of the Rosemount 3095FB Multi

Variable Transmitter
The 3095FB module has two sets of DIP switches and a jumper set which must
be setup according to the wiring configuration used to connect to the Omni Flow
Computer.
All ON = Terminated Security OFF to

All OFF = Un-Terminated allow configuration
OFF o o
AC TERMINATION
o o
PULL DOWN (B)

ON
o o
PULL UP (A)
SECURITY o o
o o
ON
1 2 3
S1 S2
ON
1 2
All ON For 9600 Baud
Fig. 6. Rosemount 3095FB Multivariable Setup Switches and Jumpers
Place the security jumper in the ‘OFF’ position, this allows the Omni flow
computer to write to the 3095FB registers ensuring that the internal
configuration matches the flow computer. Both baud rate switches S1 and S2
must be set to 9600; i.e., in the ‘ON’ position. The termination switches should
be all ‘ON’ or all ‘OFF’ depending upon whether device termination is required.
8 TB-980501 21/25.72+ & 23/27.72+

Connecting the 3095FB to the Omni Flow

Computer
TERMINAL SIGNAL DESCRIPTION

1 Port #1(3) RS 485 B wire
2 Port #1(3) RS 485 A wire
5 Signal Return for 4-20mA Outputs
7 4-20mA Analog Output # 5
Fig. 7. Back Panel Termination Assignments - SV Combo Module
A
RS-485
B
+
PWR
-
Fig. 8. Rosemount 3095FB Multivariable Wiring Terminals
TB-980501 21/25.72+ & 23/27.72+ 9

3095FB Transmitter RS-485 Connections

Getting Tech Support - Two terminals are provided marked A and B, these are connected to the A and
Technical support is B terminals of other multi-dropped 3095FBs and to the Omni SV Combo module
available at:
terminals. These connections should be made using twisted pair unshielded
(281) 240-6161
wire with a minimum gauge dependent upon the distance to be run. Use 22
Email should be sent via AWG minimum, 18 AWG maximum for runs less than 1000 ft. Use 20 AWG
the WEB Page at:
minimum, 18 AWG maximum for runs of 1000 to 4000 ft. Shielded twisted pair
www.omniflow.com
cable can be used but may have an attenuating effect due to a higher
or email to:
capacitance per foot thereby limiting the maximum wire run length to less than
4000 ft.
3095FB Transmitter Power Connections and

Requirements
Terminals marked ‘+’ and ‘-‘ are provided to connect the 3095FB to a 7.5 VDC.
to 24 VDC. power supply. This power supply must be able to provide 10 mA per
installed 3095FB plus an additional 100 mA which is needed when any 3095FB
in the system is transmitting data to the flow computer. Ripple on this power
supply must be less than 2%. Wiring gauge should be selected as per the
previous paragraph and can be unshielded un-twisted pair, but for best
performance should be shielded and twisted.
4000 Ft. Maximum
Termination ON
Omni Flow Computer
No Stubs over 6 ft.
RS 485 Bus
A
MV Port #1
B
A
MV Port #2
B
A
MV Port #3
B A A A
RS-485 RS-485 RS-485
A
MV Port #4 B B B
B + + +
PWR PWR PWR
- - -
7.5 VDC to 24 VDC

Termination OFF Termination OFF Termination ON
Power Supply
150 mA Minimum
+
-
Fig. 9. Connecting The Flow Computer to Multi-dropped 3095

Transmitters
10 TB-980501 21/25.72+ & 23/27.72+

Isolation and Transient Protection Issues

The design of the 3095FB transmitter does not provide any DC isolation
between the power connections and the RS-485 connections. Applying voltages
between the power wiring and RS-485 wiring greater than the allowable
common mode voltage of a RS-485 driver circuit could damage the 3095FB.
The Omni flow computer SV port is optically isolated and can handle common
mode voltages of +/- 250 VDC with respect to chassis ground.
Inductive base transient protectors including the Rosemount Model 470, can
adversely affect the output of the 3095FB. Do not use the Model 470 for
transient protection with the 3095FB. If transient protection is desired, install
the optional ‘Transient Protection Terminal Block’ described in Appendix B of the
Rosemount 3095FB Manual (pub. 00809-0100-4738).
Wiring Considerations When Replacing a Multi-dropped

3095FB Transmitter
If downtime of other 3095FB transmitters in a multi-dropped system cannot be
tolerated, make sure to provide a suitable and safe means of disconnecting
power and signal from each individual 3095FB transmitter. Because of the
power requirements of the RS-485 the 3095FB cannot be made
‘intrinsically safe’. This means that proper safety procedures must be
followed before any covers are removed from any devices or junction
boxes located in hazardous areas. Refer to Rosemount 3095FB Manual
(publication 00809-0100-4738) for correct installation of the 3095FB
transmitter.
TB-980501 21/25.72+ & 23/27.72+ 11

Configuring the Omni Flow Computer to use

the 3095FB Multi Variable Transmitter
Configuring the Meter Run I/O
Selecting the Device Type

The existing ‘Select Turbine Y/N’ entry in the ‘Config Meter Run’ menu has
been changed to ‘Select Device Type’. Valid selections at this point are:
0 = DP Sensor
1 = Turbine Meter
2 = 3095FB Multivariable
3 = SMV 3000 Multivariable
When ‘2’ is selected above the following entries appear:
Selecting the SV Combo Module Port

The number of ports available depends upon what SV Combo Modules are fitted
in the flow computer. Ports 1 and 2 are available when SV Combo Module #1 is
fitted, ports 3 and 4 when SV Combo Module #2 is present. It is possible to have
SV ports 3 and 4 without SV ports 1 and 2 assuming SV Combo Module #2 is
the only SV module fitted.
Select Modbus Address for 3095FB

In point-to-point mode (i.e., each SV port is connected to a single 3095FB) it is
recommended that you select Modbus ID ‘1’ at this point. This is the default ID
used by Rosemount when the 3095 is shipped. In multi-drop mode each
3095FB connected to a SV port must have it’s own address which can be
between 1 and 247.
What I/O Points are Used and Why

Even though the multivariable data is obtained serially and not via analog input
channels, the flow computer must have a storage structure in RAM to place the
data. Omni has chosen to treat the data as closely as possible to that obtained
by conventional means and use the same physical I/O RAM structure as is used
for analog inputs. The main difference being that with analog and pulse inputs
you would manually assign the I/O points to be used for each input. When using
the 3095FB multi variable, the flow computer automatically assigns three I/O
point assignments for the DP, temperature and pressure sensors within the
3095FB. The I/O point numbers are allocated in the order that the 3095FBs are
configured using the above three entries (it has nothing to do with SV port or SV
module numbers). The starting I/O point for the first 3095FB configured is the
first point immediately after the last I/O point used by any other A, B, E/D, E or H
combo modules in the system (see examples on facing page).
12 TB-980501 21/25.72+ & 23/27.72+

EXAMPLE 1 CONFIGURATION 6000 - 2A - 1B – 1SV

A1 Combo Module I/O Points 1–4
B1 Combo Module I/O Points 9 – 12
st
1 3095FB Configured Uses DP=13, T=14, P=15
nd
3rd 3095FB Configured Uses DP=19, T=20, P=21
th
Fig. 10. I/O Points Used by SV Combo Modules - Example 1
EXAMPLE 2 CONFIGURATION 6000 - 1A - 1E/D – 1SV

E/D1 Combo Module I/O Points 5–8
st
nd
rd
th
Bi-directional Flow and 3095FB Transmitters

Sometimes it is necessary to use a process variable obtained from a 3095FB in
more than one meter run. For example, When measuring bi-directional flow it is
customary to configure one meter run within the Omni flow computer as
‘forward’ flow and a second meter run as ‘reverse’ flow. To do this, simply
configure both meter runs as ‘Device Type = 2 (3095FB Multi Variable)’, select
the same SV port and Modbus ID, the Omni flow computer will recognize that
both meter runs are using the same 3095FB device and allocate only one set of
I/O assignments.
Referencing 3095FB Variables Elsewhere in the Configuration

While the DP, temperature and pressure obtained from the 3095FB multi
variable are used to calculate flow, it may also be necessary to use either the
temperature and/or the pressure to correct a densitometer device mounted in
close proximity. To do this simply note the I/O point numbers automatically
assigned to the 3095FB when it was configured and reuse these point numbers
as needed.
TB-980501 21/25.72+ & 23/27.72+ 13

DP, Pressure and Temperature Setup Entries Needed

Once I/O points have been assigned to the 3095FB multi variable transmitter by
the flow computer the Differential Pressure, Temperature and Pressure setup
menus become active. Data entries in these menus are:
❑ Low Alarm Setpoint

❑ High Alarm Setpoint
❑ Override Value
❑ Override Code
0 = Never Use Override Value
1 = Always Use Override Value
2 = Use Override on a 3095FB Communication Failure or Critical Error
3 = Use Last Hour’s Average on a 3095FB Communication Failure or Critical
Error
❑ 4mA Value (read only)

❑ 20mA Value (read only)
❑ Damping Code
0 = 0.108 Seconds 5 = 3.456 Seconds
2 = 0.432 Seconds 7 = 13.824 Seconds
3 = 0.864 Seconds (Default) 8 = 27.648 Seconds
4 = 1.728 Seconds
All of these data entries are changeable when using analog transmitters but
when using the 3095FB multi variable transmitter the 4mA and 20mA scaling
values cannot be changed. The upper and lower range of the 3095FB sensors
are fixed by design. The Omni flow computer simply reads these values and
displays them in the 4mA and 20mA fields for information only.
While the 3095FB transmitter has internal alarm setpoints and alarm status
points, Omni has chosen to ignore the 3095FB integral alarming functions and
use the existing flow computer alarm setpoints and alarm status points. The Low
and High Alarm Setpoints of the flow computer therefore behave exactly as they
would with an analog transmitter. The 3095FB Critical Alarm states are
monitored continuously.
Data Transferred between the 3095FB

Transmitter and the Omni Flow Computer
In operation the Omni flow computer automatically sets up the 3095FB
transmitter to use the correct floating point format and units of measure needed
to match the flow computer’s configuration. The Omni continuously reads the
following data:
❑ Process Variables DP, Pressure and Temperature

❑ Individual Transmitter Sensor Ranges
❑ Critical Transmitter Alarms (Sensor failures etc)
❑ Transmitter Information (Body and Fill material etc)
❑ Manufacturers Code
❑ Transmitter Tags
14 TB-980501 21/25.72+ & 23/27.72+

Polling Intervals for Process Variables and Critical

Alarms
The message poll scheme comprises regular reads of the process variable
values and critical alarms every 200msec per 3095FB connected to a flow
computer SV port. This means that in a multi-drop system with four transmitters
the process variable update time will be 4 x 200msec or 800msec.
Critical 3095FB Alarms Monitored By The Flow Computer

Critical alarm points within the 3095FB are monitored and mapped into the Omni
flow computer Modbus database as follows:
Alarms Associated with the 3095FB Providing Data to Meter Run ‘n’
MODBUS ACTION TAKEN IF ALARM IS ACTIVE
ALARM POINT DESCRIPTION
ADDRESS (SEE ALSO ‘FAILURE CODE SETTING’)
DP signal 10% above upper

1n83 DP transmitter failure flagged
range limit
DP signal 10% below lower
range limit
Pressure signal 10% above
1n85 Pressure transmitter failure flagged
upper range limit
Pressure signal 10% below
lower range limit
1n87 Pressure sensor is shorted Pressure transmitter failure flagged
Pressure sensor bridge is

open circuit
Temperature signal 10%
1n89 Temperature transmitter failure flagged
above upper range limit
below lower range limit
Temperature RTD is
disconnected
Sensor internal temperature DP, P and T, transmitter failures flagged
1n92
1n93
below upper range limit
Critical 3095FB sensor DP, P and T, transmitter failures flagged
1n94
electronics failure
Security jumper of 3095FB is DP, P and T transmitter failures flagged
1n95
set to ‘Write Protect’ if write to 3095FB is attempted and fails.
Note: No Communications between DP, P and T, transmitter failures flagged

^ 1n96
^ 1n96 is flow computer the Omni and 3095FB unit
generated.
TB-980501 21/25.72+ & 23/27.72+ 15

Synchronizing the 3095FB and the Flow

Computer Configurations
To ensure that the flow computer correctly interprets the 3095FB data, the flow
computer continuously verifies that the configuration of the 3095FB transmitter
matches that required by the flow computer. Additional message polls verifying
this data are interleaved with the normal message polls used to retrieve the
process variables and alarms.
Notes: Numbers in ( ) are Critical 3095FB configuration data which is checked every 10 seconds are:
Modbus addresses within
the 3095FB database ❑ Floating Point Number Format ** (0132)
** The flow computer will ❑ Measurement Engineering Units of Measure ** (0060 - 0062)
attempt to correct the
database of the 3095FB ❑ Minimum and Maximum Ranges of each Signal * (7407 - 7416)
transmitter if miss
matches are detected for ❑ Transmitter Identification (Information Only) (0001 - 0011)
these variables.
❑ Damping Factors ** (7421, 7424, 7427)
* The flow computer will
adjust its database to ❑ Transmitter ASCII Tags (3x8 characters) ** (0032 - 0047)
agree with the 3095FB ❑ Transmitter Information (Materials of Construction) (0017 - 0029)
database if miss
matches are detected for
these variables.
Viewing the 3095FB Data at the Flow
Computer Front Panel
Differential Pressure, Temperature and Pressure variables and averages are
viewed using the normal key press combinations as described in the Omni Flow
Computer User Manual.
A display list of 3095FB transmitter information can be displayed by pressing
‘Setup’ ‘n’ ‘Enter’. Data is organized by SV port number ‘n’ and in the order that
the transmitters were configured. The following information and diagnostic data
is displayed (example shows first transmitter on the #1 SV port as an example):
st
1 digit is the SV port
nd
number, 2 digit is the
Modbus Address of the SV Port 1 - 1
3095FB Manufactur
Rosemount
Model
3095/Modbus
Out Board Rev
108.0
16 TB-980501 21/25.72+ & 23/27.72+

If you continue to scroll down, the following data will be displayed:
Sensor Mod Rev

142
Sensor Serial
839193
Xmtr Ser
19644
H/W Rev
3
Modbus Rev
5
Sensor Type
GP
DP Range -250 to
250
SP Range 0-800
psi
PT Range-40 to
1200F
Isolator Mat’l
316SS
Fill Fluid
Silicone
Flange Mtr’l
316SS
Flange Type
Coplaner
Drain/Vent
316SS
O-Ring
PTFE(Teflon)
Seal Type
None
Seal Fill
None
Seal Isolator
None
NumberofSeals
None
Installing, Replacing and Calibrating 3095FB

Transmitters
Wiring Issues
transmitter.
TB-980501 21/25.72+ & 23/27.72+ 17

18 TB-980501 21/25.72+ & 23/27.72+

Using the Omni Flow Computer to Set the Modbus

Address of the 3095FB
Getting Tech Support - The 3095FB transmitter will normally be shipped with a default Modbus address
Technical support is of ‘1’. While this is fine for a point to point installation, it will cause a problem if
available at: two or more devices have the same Modbus ID in a multi-drop scheme. The
(281) 240-6161 Modbus ID of a transmitter can be set using the ‘Configurator User Interface PC
Email should be sent via Software’ available from Rosemount. It is anticipated though that some
the WEB Page at:
situations may arise where a 3095FB transmitter must be installed or replaced
www.omniflow.com
without this software being available. In this case the Omni flow computer can
or email to:
be connected to a 3095FB in the point to point mode using any available SV
port and the Modbus ID changed to what is required in the flow computer
configuration.
CAUTION! Proceed as follows:
This procedure involves 1. Setup the 3095FB as described previously in the section titled ‘Initial
‘broadcast’ transmitting a Setup of the Rosemount 3095FB Multi Variable Transmitter’.
Modbus address out of a
SV port. All devices
connected to this SV port 2. Setup the 3095FB to be RS-485 terminated.
will have their Modbus
address set to the ID 3. Connect the transmitter to any open SV port (terminal A to A, B to B).
broadcast. This would
The SV port should be jumpered for RS-485 termination. If this SV
cause data collisions and a
complete loss of channel is not an open channel, all 3095FB transmitters except the one
communication when more needing the address change must be disconnected.
than one 3095FB
transmitter is connected. Be
sure to temporarily
4. Apply power to the 3095FB transmitter.
disconnect any 3095FB
transmitters which 5. At the flow computer front panel press the following keys:
addresses you do not want
to change. [Alpha Shift] [Diag] The computer will enter the Diagnostic mode.
[Setup] [n] [Enter] Where ‘n’ is the SV port number that the 3095FB
is connected to.
6. The following warning screen may display ( SV port 1 is used as an

example) or the screen in (7) below will display.
SV Port # 1
This Port Currently
Configured For Use!
Continue (Y/N)?
This means that the flow computer has detected that this SV port is
currently configured to communicate with one or more transmitters. You
may or may not have selected the wrong SV port (see the cautions in
sidebar).
7. If you wish to continue with the address broadcast operation enter ‘Y’
and the following screen will display.
SV Port # 1
Change Xmtr Address
New Address
_
Idle
TB-980501 21/25.72+ & 23/27.72+ 19

8. Scroll down to ‘New Address’ and enter the address required. Press
‘Enter’ and the following message will display.
Sending New Address
9. The flow computer will wait a short time and then attempt to
communicate with the 3095FB using the new address. If
communications are established the following message will be displayed
for a few seconds.
Address Changed
The following message will display for a second or two should the
transmission fail.
Failed to Change
Should this message appear check your wiring, switch and jumper
settings and repeat the procedure.
10. Disconnect and reinstall 3095FB to the appropriate SV port for normal
operation making sure to observe the termination requirements of only
two devices at the end of a loop being terminated.
Using a Laptop PC to Trim the 3095FB Calibration

The flow computer provides no way of calibrating or trimming the output of the
3095FB multi variable transmitter. To calibrate the transmitter use the
‘Configurator User Interface PC Software’ available from Rosemount. The user
must disconnect the 3095FB needing calibrating and connect it in point to point
mode with the Laptop or PC running the Rosemount Interface Software.
Remember to follow all correct safety procedures when removing
transmitter covers or junction boxes. Read the manufacture’s warnings
and recommendations as printed in the 3095FB manual. Be aware that
when removing a transmitter from a multi-drop installation, wiring may be
disturbed and disruption of the circuit may cause a loss of all measurement
signals due to loss of power, signal or RS-485 termination.
20 TB-980501 21/25.72+ & 23/27.72+

TB-980501 21/25.72+ & 23/27.72+ 21

Rosemount™ 3095FB Multivariable Sensor

Interface Issues
Contents
information contained in Important Omni Flow Computer Compatibility Issues When Using SV
Firmware Revision
Combo Modules .................................................................................................. 3
21.72+/25.72+ and Serial Communication Module Compatibility ................................................................. 3
23/72.+/27.72+. Other Known System Incompatibilities .......................................................................... 3
Equipment Ordering Limitations .................................................................................... 3
Connectivity Issues When Connecting to the 3095FB Multivariable
Transmitters: Multi-drop versus Point-to-Point............................................... 4
Advantages of Multi-drop Configurations....................................................................... 4
Disadvantages of Multi-drop Configurations.................................................................. 4
Jumper Settings for the Omni SV Combo Module .......................................... 5
Setting the Address of the SV Combo Module .............................................................. 6
Setting the Termination Jumpers for the Each of the SV RS-485 Ports ........................ 6
Initial Setup of the Rosemount™ 3095FB Multi Variable Transmitter ........... 8
Connecting the 3095FB to the Omni Flow Computer ..................................... 9
3095FB Transmitter RS-485 Connections................................................................... 10
3095FB Transmitter Power Connections and Requirements....................................... 10
Isolation and Transient Protection Issues.................................................................... 11
Wiring Considerations When Replacing a Multi-dropped 3095FB Transmitter............ 11
Configuring the Omni Flow Computer to use the 3095FB Multi Variable
Transmitter ........................................................................................................ 12
Configuring the Meter Run I/O..................................................................................... 12
Selecting the Device Type ........................................................................................................ 12
Selecting the SV Combo Module Port ...................................................................................... 12
Select Modbus Address for 3095FB ......................................................................................... 12
What I/O Points are Used and Why .......................................................................................... 12
DP, Pressure and Temperature Setup Entries Needed............................................... 14
Data Transferred between the 3095FB Transmitter and the Omni Flow
Computer ........................................................................................................... 14
Polling Intervals for Process Variables and Critical Alarms ......................................... 15
Critical 3095FB Alarms Monitored By The Flow Computer ......................................... 15
Synchronizing the 3095FB and the Flow Computer Configurations........... 16
TB-980501 21/25.72+ & 23/27.72+ 1

Viewing the 3095FB Data at the Flow Computer Front Panel ...................... 16
Installing, Replacing and Calibrating 3095FB Transmitters......................... 17
Wiring Issues ............................................................................................................... 17
Using the Omni Flow Computer to Set the Modbus Address of the 3095FB ............... 19
Using a Laptop PC to Trim the 3095FB Calibration ..................................................... 20
Scope
Firmware Revisions 21.72+/25.72+ and 23.72+/27.72+ of Omni 6000/Omni
3000 Flow Computers are affected by the issues contained in this technical
bulletin. This Bulletin applies to Orifice/Differential Pressure Liquid Flow
Metering Systems and to Orifice Gas Flow Metering Systems.
Abstract
Getting Tech Support - The Rosemount 3095FB Multivariable sensor assembly is used to measure
Technical support is differential pressure (DP), static pressure (SP) and line temperature (T).
available at:
Application of the 3095FB is limited to flow computer revisions 21, 23, 25 and
(281) 240-6161
27 which work with differential head devices such as orifice meters, nozzles and
Email should be sent via venturi meters. Because the flow computer is limited to a maximum of four
the WEB Page at:
meter runs it is also limited to a maximum of four 3095FB multivariable
www.omniflow.com
transmitters.
or email to:
techsupport@omniflow.com Data is accessed from the 3095FB transmitter via a 2 wire RS-485 data link at
9600 baud using Modbus protocol. Technically, it would have been possible to
use one of the flow computer’s standard serial ports to communicate with the
3095FB but this would have caused several problems:
T Reduced the number of serial ports available for use with SCADA, PLCs
and OmniCom etc.
T Extra 'A’ type combo modules would have to be purchased simply to
provide analog outputs in a minimum system requiring just the
multivariables.
Omni chose to design a special ‘SV’ combo module which includes two 2 wire
RS-485 ports and six 4-20 mA analog outputs. With this module it becomes
possible to provide a powerful Omni 3000 system with the following specs:
T Four meter runs with Differential Pressure, Static Pressure and
Temperature inputs.
T Four communication ports for SCADA, PLC, Printer, OmniCom etc.
T Twelve Digital I/O for logic control
T Six digital to analog outputs.
This SV module is capable of connecting to one to four 3095FBs in various
multi-drop configurations. A second SV combo module can be utilized in
applications where point to point operation of more than two multivariable
transmitters is desirable.
2 TB-980501 21/25.72+ & 23/27.72+

TB-980501 Rosemount™ 3095FB Multivariable Sensor Interface Issues
Important Omni Flow Computer Compatibility

Issues When Using SV Combo Modules
The ‘SV’ combo modules are effectively serial I/O modules which have been
specially designed to communicate with various multivariable transmitters.
Changes have been made to the IRQ priorities to accommodate these ‘SV’
combo modules. These IRQ changes also involve the ‘Serial I/O Combo
Modules’ that are used to connect to printers, OmniCom, PLCs and SCADA
devices.
Serial Communication Module Compatibility

‘SV’ combo modules cannot be installed in flow computer systems containing
RS-232-C Serial I/O Combo modules model type 68-6005. The IRQ settings on
the 68-6005 serial combo module are not jumper selectable and are
incompatible with the 'SV’ combo modules. The flow computer will not be able to
initialize or boot up if this module is installed (this will be evident by a blank LCD
screen which flashes its backlighting on and off every 1.5 seconds).
The more recent 68-6205 serial module which is both RS-232-C and RS-485
compatible, has jumper selectable IRQ settings, these must be installed in the
‘IRQ 3’ position when an ‘SV’ combo module is present (see technical bulletin
TB-980503 for more details).
Other Known System Incompatibilities

At the time this bulletin was prepared, it was not possible to install both an ‘SV’
combo module and an ‘HV’ (Honeywell multivariable) combo module.
Equipment Ordering Limitations

Because of the compatibility issues raised in the above paragraphs, it is not
possible for the customer to retrofit existing flow computer installations with ‘SV’
combo modules. Any system which requires ‘SV’ combo modules, must be
purchased new from Omni, or the system must be returned to Omni to be
modified (contact a sales person at Omni for upgrade details and pricing).
TB-980501 21/25.72+ & 23/27.72+ 3

Connectivity Issues When Connecting to the

3095FB Multivariable Transmitters: Multi-drop
versus Point-to-Point
The 3095 FB multivariable transmitter is a four wire device, two power wires and
two wires for the RS-485 serial communication link. It can be connected in a
‘point-to-point’ or ‘multi-drop’ wiring configuration.
Advantages of Multi-drop Configurations

The advantages of multi-drop configurations are:
T Possibly less wire may be needed to connect devices under certain
conditions. This may or may not be the case depending upon
equipment placement.
T One Omni SV Combo module can handle up to four 3095 FB
multivariable transmitters. An Omni 3000 can be used in place of an
Omni 6000 and handle four meter runs.
Disadvantages of Multi-drop Configurations

Disadvantages of multi-drop configurations are:
T Multiple Modbus IDs required. Each multi-dropped transmitter must
have a unique Modbus ID which matches the Modbus ID selected within
the flow computer for that meter run multivariable.
T Possibility of errors when replacing multivariable transmitters.
Because of the multiple Modbus addresses it is not possible to simply
take a transmitter off the shelf and install it in a multi-drop configuration.
This is because transmitters come from Rosemount with the Modbus
address defaulted to ‘1’ and there may already be a transmitter in the loop
using that address. Adding a second transmitter with the same address
as an existing transmitter would effectively cause a loss of signal on both
transmitters (existing and new). Depending upon where the transmitter is
in the wiring, ‘termination’ jumpers may or may not be required on the
replacement transmitter (see below).
T Transmitter interaction is possible. While not likely, a hardware failure
in one transmitter could compromise the integrity of the shared RS-485
link causing a loss of flow signals for all meter runs. Calibrating a
transmitter via a laptop computer requires the wiring to be disturbed, care
must be taken not to disconnect other transmitters in the same multi-drop
loop.
4 TB-980501 21/25.72+ & 23/27.72+

T RS-485 termination requirements more complex. RS-485 transmission

wires must have only one beginning and one end (they cannot be used in
a ‘star’ configuration). Both ends of the wire must be terminated, meaning
only two devices in the loop need terminating. In a point-to-point
configuration, this simply means both the flow computer and transmitter
are terminated. In a multi-drop configuration, the user must ensure that
only the end devices have the termination jumpers in. This means that
some transmitters may have the terminating jumpers in while others may
have them out. Remember that the Omni may or may not be at the end of
the wire so it may or may not be one of the terminated devices.
T Process variable update time may exceed the flow computers 500
msec cycle time. Critical measurement or control systems require that
the process variables be input to the flow computer as fast as possible for
best performance.
Jumper Settings for the Omni SV Combo

Module
The Multi Variable ‘SV’ Combo module contains several sets of jumpers which
must be installed correctly (see figure below).
Port 1 (3) Port 2 (4)

Tx/RTS Leds Red Tx/RTS Leds Red
Recv Led Grn Recv Led Grn
RTS GND
T T
SV RS-485 Termination Jum p ers E E
R R SV Port 1 ( 3 )
Both Jm pers In = Port Terminated M M
Both Jm pers Out = Port Non-Terminated
Alway s RTS RTS GND

T T
E E
SV Address Jum p er R R SV Port 2 ( 4 )
Jm p In = 1st SV Combo M M
Jm p Out = 2nd SV Combo
Port Numbers in ( ) are for 2nd SV Module

A lway s IRQ 2 BRD SEL
2 4 IRQ
Fig. 1. Omni Model 68-6203 Multivariable Interface Module - SV Combo

Module
TB-980501 21/25.72+ & 23/27.72+ 5

Setting the Address of the SV Combo Module

The flow computer can accept up to two ‘SV’ Combo modules, each with a
unique address determined by the ‘BRD SEL’ jumper shown in Figure 1. With
this jumper fitted the flow computer will report that a ‘SV1’ module is installed
and SV ports 1 and 2 will be available. Without this jumper in the ‘BRD SEL’
position the flow computer will report that a ‘SV2’ module is installed and SV
ports 3 and 4 will be available. Note that a system can have a ‘SV2’ module
without a ‘SV1’ being installed, in this case only SV ports 3 and 4 would be
available.
Setting the Termination Jumpers for the Each of the SV

RS-485 Ports
Multivariable RS-485 communication circuits must have two ends only, a ‘star’
configuration with more than two ends or a ‘loop’ configuration with no
ends is not allowed. The devices at both ends of the circuit must be jumpered
to provide termination.
3095 FB 3095 FB 3095 FB 3095 FB

MV MV MV MV
ID #1 ID #2 ID #3 ID #4
Omni
Flow
Computer
This Device This Device
Must Be Must Be
Fig. 2. Multi-drop Configuration with Flow Computer Terminated
Both jumpers marked ‘TERM’ must be installed to terminate a flow computer

‘SV’ port (see Fig. 1 previous page). Termination settings for the 3095FB are
shown later in this document.
3095 FB This Device 3095 FB

MV Must Be MV
ID #1 Terminated ID #4
Omni
Flow
Computer
This Device
Must Be
3095 FB 3095 FB
MV MV
Terminated
ID #2 ID #3
Fig. 3. Multi-drop Configuration with Flow Computer Non-terminated
6 TB-980501 21/25.72+ & 23/27.72+

3095 FB 3095 FB 3095 FB 3095 FB

MV MV MV MV
ID #1 ID #2 ID #3 ID #4
Omni
Flow
Computer
Star Configuration Not Allowed!
Fig. 4. Unacceptable Configuration - Five Termination Points
All 4 MV Ports of 3095 FB 3095 FB 3095 FB 3095 FB

Flow Computer MV MV MV MV
Must Be Terminated ID #1 ID #1 ID #1 ID #1
Omni
Flow
Computer
Using
Independent
MV Ports Modbus IDs of 3095FBs All Four 3095FB
Can Be The Same In This Transmitters
Point to Point Configuration Must Be Terminated
In the point-to-point configuration each 3095FB transmitter is connected to an

independent ‘SV’ port of the flow computer. Because each ‘SV’ port is now
connected to only one 3095FB, each 3095FB can now use the default Modbus
address ‘1’, greatly simplifying transmitter replacement issues discussed later in
this document.
TB-980501 21/25.72+ & 23/27.72+ 7

Initial Setup of the Rosemount™ 3095FB Multi

Variable Transmitter
The 3095FB module has two sets of DIP switches and a jumper set which must
be setup according to the wiring configuration used to connect to the Omni Flow
Computer.
All ON = Terminated Security OFF to

All OFF = Un-Terminated allow configuration
OFF o o
AC TERMINATION
o o
PULL DOWN (B)

ON
o o
PULL UP (A)
SECURITY o o
o o
ON
1 2 3
S1 S2
ON
1 2
All ON For 9600 Baud
Fig. 6. Rosemount™ 3095FB Multivariable Setup Switches and Jumpers
Place the security jumper in the ‘OFF’ position, this allows the Omni flow
computer to write to the 3095FB registers ensuring that the internal
configuration matches the flow computer. Both baud rate switches S1 and S2
must be set to 9600; i.e., in the ‘ON’ position. The termination switches should
be all ‘ON’ or all ‘OFF’ depending upon whether device termination is required.
8 TB-980501 21/25.72+ & 23/27.72+

Connecting the 3095FB to the Omni Flow

Computer
TERMINAL SIGNAL DESCRIPTION

Fig. 7. Back Panel Termination Assignments - SV Combo Module
A
RS-485
B
+
PWR
-
Fig. 8. Rosemount™ 3095FB Multivariable Wiring Terminals
TB-980501 21/25.72+ & 23/27.72+ 9

3095FB Transmitter RS-485 Connections

Getting Tech Support - Two terminals are provided marked A and B, these are connected to the A and
Technical support is B terminals of other multi-dropped 3095FBs and to the Omni SV Combo module
available at:
terminals. These connections should be made using twisted pair unshielded
(281) 240-6161
wire with a minimum gauge dependent upon the distance to be run. Use 22
Email should be sent via AWG minimum, 18 AWG maximum for runs less than 1000 ft. Use 20 AWG
the WEB Page at:
minimum, 18 AWG maximum for runs of 1000 to 4000 ft. Shielded twisted pair
www.omniflow.com
cable can be used but may have an attenuating effect due to a higher
or email to:
capacitance per foot thereby limiting the maximum wire run length to less than
4000 ft.
3095FB Transmitter Power Connections and

Requirements
Terminals marked ‘+’ and ‘-‘ are provided to connect the 3095FB to a 7.5 VDC.
to 24 VDC. power supply. This power supply must be able to provide 10 mA per
installed 3095FB plus an additional 100 mA which is needed when any 3095FB
in the system is transmitting data to the flow computer. Ripple on this power
supply must be less than 2%. Wiring gauge should be selected as per the
previous paragraph and can be unshielded un-twisted pair, but for best
performance should be shielded and twisted.
Fig. 9. The labels for the Rosemount 3095 RS-485 serial port are
reversed. Label A is actually the B (negative signal) and Label B is
actually the A (positive signal).
10 TB-980501 21/25.72+ & 23/27.72+

Isolation and Transient Protection Issues

The design of the 3095FB transmitter does not provide any DC isolation
between the power connections and the RS-485 connections. Applying voltages
between the power wiring and RS-485 wiring greater than the allowable
common mode voltage of a RS-485 driver circuit could damage the 3095FB.
The Omni flow computer SV port is optically isolated and can handle common
mode voltages of +/- 250 VDC with respect to chassis ground.
Inductive base transient protectors including the Rosemount Model 470, can
adversely affect the output of the 3095FB. Do not use the Model 470 for
transient protection with the 3095FB. If transient protection is desired, install
the optional ‘Transient Protection Terminal Block’ described in Appendix B of the
Rosemount 3095FB Manual (pub. 00809-0100-4738).
Wiring Considerations When Replacing a Multi-dropped

3095FB Transmitter
transmitter.
TB-980501 21/25.72+ & 23/27.72+ 11

Configuring the Omni Flow Computer to use

the 3095FB Multi Variable Transmitter
Configuring the Meter Run I/O
Selecting the Device Type

The existing ‘Select Turbine Y/N’ entry in the ‘Config Meter Run’ menu has
been changed to ‘Select Device Type’. Valid selections at this point are:
0 = DP Sensor
1 = Turbine Meter
2 = 3095FB Multivariable
3 = SMV 3000 Multivariable
When ‘2’ is selected above the following entries appear:
Selecting the SV Combo Module Port

The number of ports available depends upon what SV Combo Modules are fitted
in the flow computer. Ports 1 and 2 are available when SV Combo Module #1 is
fitted, ports 3 and 4 when SV Combo Module #2 is present. It is possible to have
SV ports 3 and 4 without SV ports 1 and 2 assuming SV Combo Module #2 is
the only SV module fitted.
Select Modbus Address for 3095FB

In point-to-point mode (i.e., each SV port is connected to a single 3095FB) it is
recommended that you select Modbus ID ‘1’ at this point. This is the default ID
used by Rosemount when the 3095 is shipped. In multi-drop mode each
3095FB connected to a SV port must have it’s own address which can be
between 1 and 247.
What I/O Points are Used and Why

Even though the multivariable data is obtained serially and not via analog input
channels, the flow computer must have a storage structure in RAM to place the
data. Omni has chosen to treat the data as closely as possible to that obtained
by conventional means and use the same physical I/O RAM structure as is used
for analog inputs. The main difference being that with analog and pulse inputs
you would manually assign the I/O points to be used for each input. When using
the 3095FB multi variable, the flow computer automatically assigns three I/O
point assignments for the DP, temperature and pressure sensors within the
3095FB. The I/O point numbers are allocated in the order that the 3095FBs are
configured using the above three entries (it has nothing to do with SV port or SV
module numbers). The starting I/O point for the first 3095FB configured is the
first point immediately after the last I/O point used by any other A, B, E/D, E or H
combo modules in the system (see examples on facing page).
12 TB-980501 21/25.72+ & 23/27.72+

EXAMPLE 1 CONFIGURATION 6000 - 2A - 1B – 1SV

B1 Combo Module I/O Points 9 – 12
st
nd
3rd 3095FB Configured Uses DP=19, T=20, P=21
th
EXAMPLE 2 CONFIGURATION 6000 - 1A - 1E/D – 1SV

E/D1 Combo Module I/O Points 5–8
st
nd
rd
th
Bi-directional Flow and 3095FB Transmitters

Sometimes it is necessary to use a process variable obtained from a 3095FB in
more than one meter run. For example, When measuring bi-directional flow it is
customary to configure one meter run within the Omni flow computer as
‘forward’ flow and a second meter run as ‘reverse’ flow. To do this, simply
configure both meter runs as ‘Device Type = 2 (3095FB Multi Variable)’, select
the same SV port and Modbus ID, the Omni flow computer will recognize that
both meter runs are using the same 3095FB device and allocate only one set of
I/O assignments.
Referencing 3095FB Variables Elsewhere in the Configuration

While the DP, temperature and pressure obtained from the 3095FB multi
variable are used to calculate flow, it may also be necessary to use either the
temperature and/or the pressure to correct a densitometer device mounted in
close proximity. To do this simply note the I/O point numbers automatically
assigned to the 3095FB when it was configured and reuse these point numbers
as needed.
TB-980501 21/25.72+ & 23/27.72+ 13

DP, Pressure and Temperature Setup Entries Needed

Once I/O points have been assigned to the 3095FB multi variable transmitter by
the flow computer the Differential Pressure, Temperature and Pressure setup
menus become active. Data entries in these menus are:
T Low Alarm Setpoint

T High Alarm Setpoint
T Override Value
T Override Code
0 = Never Use Override Value
1 = Always Use Override Value
2 = Use Override on a 3095FB Communication Failure or Critical Error
3 = Use Last Hour’s Average on a 3095FB Communication Failure or Critical
Error
T 4mA Value (read only)
T 20mA Value (read only)
T Damping Code
2 = 0.432 Seconds 7 = 13.824 Seconds
3 = 0.864 Seconds (Default) 8 = 27.648 Seconds
4 = 1.728 Seconds
All of these data entries are changeable when using analog transmitters but
when using the 3095FB multi variable transmitter the 4mA and 20mA scaling
values cannot be changed. The upper and lower range of the 3095FB sensors
are fixed by design. The Omni flow computer simply reads these values and
displays them in the 4mA and 20mA fields for information only.
While the 3095FB transmitter has internal alarm setpoints and alarm status
points, Omni has chosen to ignore the 3095FB integral alarming functions and
use the existing flow computer alarm setpoints and alarm status points. The Low
and High Alarm Setpoints of the flow computer therefore behave exactly as they
would with an analog transmitter. The 3095FB Critical Alarm states are
monitored continuously.
Data Transferred between the 3095FB

Transmitter and the Omni Flow Computer
In operation the Omni flow computer automatically sets up the 3095FB
transmitter to use the correct floating point format and units of measure needed
to match the flow computer’s configuration. The Omni continuously reads the
following data:
T Process Variables DP, Pressure and Temperature

T Individual Transmitter Sensor Ranges
T Critical Transmitter Alarms (Sensor failures etc)
T Transmitter Information (Body and Fill material etc)
T Manufacturers Code
T Transmitter Tags
14 TB-980501 21/25.72+ & 23/27.72+

Polling Intervals for Process Variables and Critical

Alarms
The message poll scheme comprises regular reads of the process variable
values and critical alarms every 200msec per 3095FB connected to a flow
computer SV port. This means that in a multi-drop system with four transmitters
the process variable update time will be 4 x 200msec or 800msec.
Critical 3095FB Alarms Monitored By The Flow Computer

Critical alarm points within the 3095FB are monitored and mapped into the Omni
flow computer Modbus database as follows:
Alarms Associated with the 3095FB Providing Data to Meter Run ‘n’
MODBUS ACTION TAKEN IF ALARM IS ACTIVE
ALARM POINT DESCRIPTION
ADDRESS (SEE ALSO ‘FAILURE CODE SETTING’)
DP signal 10% above upper

range limit
DP signal 10% below lower
range limit
Pressure signal 10% above
upper range limit
Pressure signal 10% below
lower range limit
1n87 Pressure sensor is shorted Pressure transmitter failure flagged
Pressure sensor bridge is

open circuit
below lower range limit
Temperature RTD is
disconnected
1n92
1n93
below upper range limit
Critical 3095FB sensor DP, P and T, transmitter failures flagged
1n94
electronics failure
Security jumper of 3095FB is DP, P and T transmitter failures flagged
1n95
set to ‘Write Protect’ if write to 3095FB is attempted and fails.
Note: No Communications between DP, P and T, transmitter failures flagged

^ 1n96
^ 1n96 is flow computer the Omni and 3095FB unit
generated.
TB-980501 21/25.72+ & 23/27.72+ 15

Synchronizing the 3095FB and the Flow

Computer Configurations
To ensure that the flow computer correctly interprets the 3095FB data, the flow
computer continuously verifies that the configuration of the 3095FB transmitter
matches that required by the flow computer. Additional message polls verifying
this data are interleaved with the normal message polls used to retrieve the
process variables and alarms.
Notes: Numbers in ( ) are Critical 3095FB configuration data which is checked every 10 seconds are:
Modbus addresses within
the 3095FB database T Floating Point Number Format ** (0132)
** The flow computer will T Measurement Engineering Units of Measure ** (0060 - 0062)
attempt to correct the
database of the 3095FB T Minimum and Maximum Ranges of each Signal * (7407 - 7416)
transmitter if miss
T Transmitter Identification (Information Only) (0001 - 0011)
these variables. T Damping Factors ** (7421, 7424, 7427)
* The flow computer will T Transmitter ASCII Tags (3x8 characters) ** (0032 - 0047)
adjust its database to
agree with the 3095FB T Transmitter Information (Materials of Construction) (0017 - 0029)
database if miss
Viewing the 3095FB Data at the Flow

these variables.
Computer Front Panel

Differential Pressure, Temperature and Pressure variables and averages are
viewed using the normal key press combinations as described in the Omni Flow
Computer User Manual.
A display list of 3095FB transmitter information can be displayed by pressing
‘Setup’ ‘n’ ‘Enter’. Data is organized by SV port number ‘n’ and in the order that
the transmitters were configured. The following information and diagnostic data
is displayed (example shows first transmitter on the #1 SV port as an example):
st
1 digit is the SV port
nd
number, 2 digit is the
Modbus Address of the SV Port 1 - 1
3095FB Manufactur
Rosemount
Model
3095/Modbus
Out Board Rev
108.0
16 TB-980501 21/25.72+ & 23/27.72+

If you continue to scroll down, the following data will be displayed:
Sensor Mod Rev

142
Sensor Serial
839193
Xmtr Ser
19644
H/W Rev
3
Modbus Rev
5
Sensor Type
GP
DP Range -250 to
250
SP Range 0-800
psi
PT Range-40 to
1200F
Isolator Mat’l
316SS
Fill Fluid
Silicone
Flange Mtr’l
316SS
Flange Type
Coplaner
Drain/Vent
316SS
O-Ring
PTFE(Teflon)
Seal Type
None
Seal Fill
None
Seal Isolator
None
NumberofSeals
None
Installing, Replacing and Calibrating 3095FB

Transmitters
Wiring Issues
TB-980501 21/25.72+ & 23/27.72+ 17


transmitter.
18 TB-980501 21/25.72+ & 23/27.72+

Using the Omni Flow Computer to Set the Modbus

Address of the 3095FB
Getting Tech Support - The 3095FB transmitter will normally be shipped with a default Modbus address
Technical support is of ‘1’. While this is fine for a point to point installation, it will cause a problem if
available at: two or more devices have the same Modbus ID in a multi-drop scheme. The
(281) 240-6161 Modbus ID of a transmitter can be set using the ‘Configurator User Interface PC
Email should be sent via Software’ available from Rosemount. It is anticipated though that some
the WEB Page at:
situations may arise where a 3095FB transmitter must be installed or replaced
www.omniflow.com
without this software being available. In this case the Omni flow computer can
or email to:
be connected to a 3095FB in the point to point mode using any available SV
port and the Modbus ID changed to what is required in the flow computer
configuration.
CAUTION! Proceed as follows:
n n
This procedure involves 1. Setup the 3095FB as described previously in the section titled ‘Initial
‘broadcast’ transmitting a Setup of the Rosemount 3095FB Multi Variable Transmitter’.
Modbus address out of a
SV port. All devices
connected to this SV port 2. Setup the 3095FB to be RS-485 terminated.
will have their Modbus
address set to the ID 3. Connect the transmitter to any open SV port (terminal A to A, B to B).
broadcast. This would
cause data collisions and a The SV port should be jumpered for RS-485 termination. If this SV
complete loss of channel is not an open channel, all 3095FB transmitters except the one
communication when more needing the address change must be disconnected.
than one 3095FB
transmitter is connected. Be
sure to temporarily 4. Apply power to the 3095FB transmitter.
disconnect any 3095FB
transmitters which 5. At the flow computer front panel press the following keys:
addresses you do not want
to change. [Alpha Shift] [Diag] The computer will enter the Diagnostic mode.
[Setup] [n] [Enter] Where ‘n’ is the SV port number that the 3095FB
is connected to.
6. The following warning screen may display ( SV port 1 is used as an

example) or the screen in (7) below will display.
SV Port # 1
This Port Currently
Configured For Use!
Continue (Y/N)?
This means that the flow computer has detected that this SV port is
currently configured to communicate with one or more transmitters. You
may or may not have selected the wrong SV port (see the cautions in
sidebar).
7. If you wish to continue with the address broadcast operation enter ‘Y’
and the following screen will display.
SV Port # 1
Change Xmtr Address
New Address
_
Idle
TB-980501 21/25.72+ & 23/27.72+ 19

8. Scroll down to ‘New Address’ and enter the address required. Press
‘Enter’ and the following message will display.
Sending New Address
9. The flow computer will wait a short time and then attempt to
communicate with the 3095FB using the new address. If
communications are established the following message will be displayed
for a few seconds.
Address Changed
The following message will display for a second or two should the
transmission fail.
Failed to Change
Should this message appear check your wiring, switch and jumper
settings and repeat the procedure.
10. Disconnect and reinstall 3095FB to the appropriate SV port for normal
operation making sure to observe the termination requirements of only
two devices at the end of a loop being terminated.
Using a Laptop PC to Trim the 3095FB Calibration

The flow computer provides no way of calibrating or trimming the output of the
3095FB multi variable transmitter. To calibrate the transmitter use the
‘Configurator User Interface PC Software’ available from Rosemount. The user
must disconnect the 3095FB needing calibrating and connect it in point to point
mode with the Laptop or PC running the Rosemount Interface Software.
Remember to follow all correct safety procedures when removing
transmitter covers or junction boxes. Read the manufacture’s warnings
and recommendations as printed in the 3095FB manual. Be aware that
when removing a transmitter from a multi-drop installation, wiring may be
disturbed and disruption of the circuit may cause a loss of all measurement
signals due to loss of power, signal or RS-485 termination.
20 TB-980501 21/25.72+ & 23/27.72+

TB-980501 21/25.72+ & 23/27.72+ 21

Communicating with Honeywell SMV3000

Multivariable Transmitters
Contents
information contained in the DE Protocol Overview ........................................................................................ 2
User Manual, and is
revisions .72+.
The Honeywell Handheld Communicator...................................................... 3
Combo Module LED Status Indicators ............................................................. 3
Communication with
Honeywell SMV3000 Switching Between Analog and Digital Mode.................................................. 3
Smart Transmitters - This
feature allows you to
Viewing the Status of the Honeywell Transmitter from the Keypad ............. 4
communicate with Viewing the Status of the Honeywell Transmitter from the Keypad .......... 5
Honeywell SMV3000 Smart
Multivariable Transmitters Obtaining More Detailed Status Information from the Keypad...................... 8
which provide Differential
Pressure , Temperature and Transducer Alarms Logged by the Flow Computer...................................... 12
Static Pressure, via Omni’s HV Combo Module Address Jumpers ............................................................ 13
HV type Process I/O Combo
Modules and using How the I/O Points are Assigned .................................................................... 14
OmniCom Revision........................................................................................... 15

available at:
(281) 240-6161 Scope
the WEB Page at: All firmware revisions of Omni 6000/Omni 3000 Flow Computers containing
www.omniflow.com firmware 21.72+, 23.72+, 27.72+ are able to communicate with Honeywell
or email to: SMV3000 Smart Multivariable Transmitters. This feature uses Honeywell’s DE
techsupport@omniflow.com Protocol and requires that an HV Combo I/O Module be installed in your flow
computer.
TB-980502 21/23/27.72+ 1
Abstract
Using an ‘HV’ Combo I/O Module, the Omni Flow Computer can communicate
with up to 4 Honeywell SMV3000 Smart Multivariable transmitters. These
transmitters provide Differential Pressure, Temperature and Pressure signals
using Honeywell’s DE Protocol. Only one ‘HV’ Type Combo Module can be
installed in the flow computer. Loop power is provided by the ‘HV’ combo
module.
DE Protocol Overview
Digital data is transmitted serially between the flow computer and Honeywell
Smart Transmitters by modulating the current in the two wire loop connecting
is transmitted at 218.47 bits per second with a digital ‘0’ = 20 mA and a digital ‘1’
= 4 mA.
In normal operation, the Honeywell transmitter operates in the ‘6-byte Burst
Mode’. In this mode, the transmitter transmits the following data to the flow
computer every 366 msec:
Byte #5 Database ID (indicates where in the transmitters database Byte #6
below belongs)
maintains an exact copy of the multivariable transmitters configuration database.
The transmitter database which is sent to the Omni flow computer is about 132
bytes. Based on the burst rate of the transmitter it can take about 45 to 55
seconds to completely build a copy of the transmitter database within the flow
computer. The transmitter database is continuously compared against the flow
computer configuration settings for that transmitter. The flow computer
2 TB-980502 21/23/27.72+
The Honeywell Handheld Communicator

transmitter:
(1) Lower Range Value or Zero
(2) Transmitter Span or Max Range
(3) Damping Factor
(4) Tag Name
(5) DP, SP and Temperature conformance bits
Any changes made to 1, 2, 3 and 5 using the handheld communicator will be
overwritten by the flow computer. In the digital mode it is not absolutely
necessary to calibrate the transmitters outputs using the handheld
communicator. The user can however trim the transmitters output calibration
using the handheld communicator if he so desires without interference from the
flow computer (see Honeywell documentation for details of trimming corrects).
Whether the transmitter is trimmed with the handheld or not, the digital signals
should be final calibrated ‘end to end’ using the normal analog input method
described in Chapter 8 of Volume 1.

Each I/O channel of the ‘HV’ Combo module has a set of two LED indicators,
one green and one red. The green LED shows all communication activity taking
transmitter.

Connecting an analog mode Honeywell multivariable transmitter to the computer
will cause the flow computer to automatically switch the transmitter to the digital
DE mode sending out a series of ‘Wake up commands’ to the Honeywell
transmitter. A switch over to the digital mode by the transmitter will cause the
green LED on the combo module to pulse steadily indicating that
communications have been established.
To disable the wake up command and initialize communications between the
Honeywell transmitter and the flow computer, delete all I/O point assignments
within the flow computer to that I/O point. Using the Honeywell handheld
communicator press [Shift] [A/D] and wait till the handheld displays ‘Change to
Analog?’ Answer by pressing [Enter] (Yes). ‘SFC Working’ will be displayed.
The green LED on the ‘HV’ Combo module on that channel will stop pulsing. Re-
entering the I/O point will cause the Omni to send the wake up command to the
Honeywell and after three command sends the green LED on the Honeywell
module will pulse at a steady 3Hz rate.
TB-980502 21/23/27.72+ 3
Viewing the Status of the Honeywell

To verify the data being received from the smart transmitter, press [Input]
[Status] and [Enter] from the front panel. The following data displays:
HV-1 Transmitter
DB Status
OK
Gstatus NON-
CRITICAL
DP%
25.00
SP%
76.50
TT%
32.13
DP LRV
0.0
DP Span
400.0
DP Damp Secs.
.16
DP Conformity bit
0
SP LRV
406.8
SP Span
27680.2
SP Damp Secs
.16
SP Conformity bit
0
TT LRV
.0
TT Span
100.0
TT Damp Secs
.3
TT Conformity bit
0
SW Revision
2.1
Serial #
xxxxxxxxxx
DP Range
400.0
SP Range
20760.5
TT Range
850.0
ID/TAG SMV-
3000
Filter Hertz
60
SensorType RTD-
PT100
4 TB-980502 21/23/27.72+

HV-1 Transmitter : Indicates the Honeywell Multivariable Combo Module
(HV) and the channel number on that module. As there
can be only one HV module installed, this number can
only be 1 through 4.
DB Status : There are five status states.
transducer.
30-45 sec or so.
Burst Mode. Because the flow computer
will not tolerate this mode of operation, this
status display should only be displayed
momentarily as the flow computer will
automatically switch the transmitter into
the 6-Byte Burst Mode.
TB-980502 21/23/27.72+ 5
Gstatus : Gross Status Flag value:

1) OK : No errors are reported by the SMV
transmitter.
2) Critical Critical error reported by the SMV
transmitter.
3) Non-Critical : An error of a non critical nature has been
reported by the SMV transmitter.
4) Reserved : Consult Honeywell if this status value is
returned.
DP% : Differential pressure variable value in percentage of the
previous).
SP% : Static pressure variable value in percentage of the
previous).
TT% : Temperature variable value in percentage of the
previous).
DP LRV : Lower Range Value of the DP variable in engineering
units. Engineering units are inches of water at 39
degrees Fahrenheit.
DP Span : The Span of the Differential pressure variable in
engineering units (the span is the difference between the
lower and upper ranges of the transmitter). Engineering
units are inches of water at 39 degrees Fahrenheit. The
flow computer will display ‘DB Error’ if the user tries to
enter a span of 0% or a span which would exceed the DP
sensor ‘range’ (described later).
DP Damp Secs : Damping Time of the DP transmitter output in seconds.
DP Conformity Bit : Meaningful only with differential pressure transmitters.

square root output. The flow computer requires linear
output and will automatically set this bit to 0 should it be
set to a 1.
SP LRV : Lower Range Value of the Static Pressure variable in
engineering units. Engineering units are inches of water
at 39 degrees Fahrenheit.
SP Span : The Span of the Static Pressure variable in engineering
inches of water at 39 degrees Fahrenheit. The flow
computer will display ‘DB Error’ if the user tries to enter a
span of 0% or a span which would exceed the static
pressure sensor ‘range’ (described later).
6 TB-980502 21/23/27.72+
SP Damp Secs : Damping Time of the Static Pressure transmitter output in

seconds.
SP Conformity Bit : Meaningful only with differential pressure transmitters.
TT LRV : Lower Range Value of the temperature variable in
engineering units. Engineering units are degrees Celsius.
TT Span : The Span of the Temperature variable in engineering
degrees Celsius. The flow computer will display ‘DB
Error’ if the user tries to enter a span of 0% or a span
which would exceed the temperature sensor ‘range’
(described later).
TT Damp Secs : Damping Time of the Temperature transmitter output in
seconds.
TT Conformity Bit : Meaningful only with differential pressure transmitters.

Software Revision : Current Software installed within the smart multivariable
device.
Serial # : Serial Number of the smart multivariable device.
DP Range : Maximum range of the DP sensor in inches of water at 39
degrees Fahrenheit. The transmitter will not accept
configuration entries which exceed this value.
SP Range : Maximum range of the Static Pressure sensor in inches
of water at 39 degrees Fahrenheit. The transmitter will
not accept configuration entries which exceed this value.
TT Range : Maximum range of the Temperature sensor in degrees
Celsius. The transmitter will not accept configuration
entries which exceed this value.
ID/TAG : ASCII string used to identify the SMV DP transmitter.
Filter Hertz : Frequency used to filter sensor signals to minimize AC
mains interference. Selections are 50 or 60 Hertz.
Sensor Type : Temperature sensor types are:
1) RTD-PT100
2) J type Thermocouple
3) K type Thermocouple
4) T type Thermocouple
5) E type Thermocouple
Note: Thermocouples can be internally or externally
compensated.
TB-980502 21/23/27.72+ 7
Obtaining More Detailed Status Information

from the Keypad
Additional data based upon the ‘Primary’, ‘Secondary’ and ‘Tertiary’ ‘Detailed
Status’ bytes which are retrieved from the SMV data base is available by
pressing [Input] [Status] [Alarm] and [Enter]. The display will approximate the
following messages depending upon certain bits being ON in the appropriate
‘detailed status byte’. Some of these status bits also cause alarm status points
within the flow computer data base to be activated. When this happens, these
alarm events are time and date tagged and logged in the alarm log as any other
flow computer alarm.
HONEYWELL OMNI
BYTE-BIT POINT(S)
ACTIVATED
Meter Body Fault: Communication between 2n44 CR
1-0 sensor board and SMV main board 2n47 CR
electronics is suspect. 2n50 CR
1-1 Characterization PROM Fault or Checksum 2n44 CR
Error 2n47 CR
1-2 Suspect Input: Possibly Meter Body or 2n44 CR
Electronics Failure 2n47 CR
1-3 DAC Compensation: Fault Detected 2n52 CR
1-4 NVM Fault: Non Volatile Memory Error 2n52 CR

Detected
1-5 RAM Fault: RAM Memory Error Detected 2n52 CR
1-6 ROM Fault: ROM Memory Error Detected 2n52 CR
2n44 CR
1-7 PAC Fault Detected
2n47 CR
2-0 MB OverTemp: Meter Body Sensor Over 2n51 NC
Temperature
2-1 DP Zero Correction Value is Outside of 2n42 NC
Acceptable Limits
2-2 DP Span Correction Value is Outside of 2n42 NC
Acceptable Limits
2-3 
meaning)
2-4 MB Overload or : (Always with next 2n47 CR
message)
8 TB-980502 21/23/27.72+
HONEYWELL OMNI
BYTE-BIT POINT(S)
ACTIVATED
2-5 Meter Body Fault: Pressure input is twice 2n47 CR
the URL
DP Cal Corr Default: ‘Reset Corrects’
2-6 command issued or ‘Calibrate and Power 2n42 NC
Cycle’ performed
2-7 DAC Tempco Data Bad: Analog mode only. 
2n44 CR
Invalid Database: Some error detected in
3-0 2n47 CR
the SMVs configuration. All PVs are suspect.
2n50 CR
3-1 Suspect SP Input: Static pressure input 2n47 CR
suspect
3-2 
meaning)
3-3 
meaning)
3-4 DP Term Out of Range 
V-T Term Out of Rng: Viscosity temperature
3-5 
term out of range
D-T Term Out of Rng: Density temperature
3-6 
term out of range
Ind Var Out of Range: Independent variable
3.7 
out of range
4-0 
meaning)
4-1 Excess Zero Corr SP: Excess zero 2n45 NC
4-2 Excess Span Corr SP: Excess span 2n45 NC
SP is Absolute: Static pressure sensor is
4-3 
absolute
SP is Gauge: Static pressure sensor is
4-4 
gauge
4-5 
meaning)
4-6 SP Corrects Reset: Static pressure 2n45 NC
corrections reset
TB-980502 21/23/27.72+ 9
HONEYWELL OMNI
BYTE-BIT POINT(S)
ACTIVATED
4-7 
meaning)
5-0 
meaning)
5-1 
meaning)
5-2 
meaning)
5-3 
meaning)
5-4 DP in Input Mode 2n43 CR
5-5 SP in Input Mode 2n46 CR
5-6 Temp in Input Mode 2n49 CR
5-7 PV4 in Input Mode 
6-3 2 Wire TC Used 
6-4 DP in Output Mode 2n43 CR
6-5 SP in Output Mode 2n46 CR
6-6 Temp in Output Mode 2n49 CR
6-7 PV4 in Output Mode 
7-0 Temp A/D Fault : Temperature A to D failure 2n50 CR
7-1 Temp Char Fault: Temperature 2n50 CR

characterization fault
7-2 Temp Input Suspect: Temperature input 2n50 CR
signal is suspect
7-3 
meaning)
7-4 Temp NVM Fault: Temperature non-volatile 2n50 CR
memory fault detected
7-5 
meaning)
10 TB-980502 21/23/27.72+
HONEYWELL OMNI
BYTE-BIT POINT(S)
ACTIVATED
7-6 
meaning)
7-7 
meaning)
Delta Temperature : (FUTURE - Consult
8-0 
8-1 Excess Zero Cor Temp 2n48 NC
8-2 Excess Span Cor Temp 2n48 NC
8-3 Temp Input Open : Open circuit 2n50 CR

temperature sensor
8-4 Temp Over Range : Process temperature is 2n50 CR
over range
Redun Backup Temp : (FUTURE - Consult
8-5 
8-6 Temp Corrects Active 2n48 NC
8-7 Temp Sensor Mismatch 2n50 CR
TB-980502 21/23/27.72+ 11
Transducer Alarms Logged by the Flow

Computer
The following alarm points are automatically updated with data contained in the
‘detailed status’ bytes within the flow computers copy of the SMVs data base
(see the previous table). These alarms are time and date tagged and logged by
the flow computer whenever the respective bit changes state. Other than the
logging function, non critical alarms cause no other action to occur. Critical
alarms are alarms which are considered to adversely impact the credibility of the
measurement reading, these alarms cause the flow computer to examine the
‘Override Code’ strategy and apply an override if so configured.
ADDRESS OF ALARM TITLE ALARM TYPE

ALARM POINT
2n42 Meter ‘n’ DP: Invalid Corrects or Corrects NC
Reset
2n43 Meter ‘n’ DP is in the Input or Output Mode CR
2n44 Meter ‘n’ DP Signal is Suspect CR
2n45 Meter ‘n’ Pressure: Invalid Corrects or Corrects NC

Reset
2n46 Meter ‘n’ Pressure is in the Input or Output CR
Mode
2n47 Meter ‘n’ Pressure Signal is Suspect CR
2n48 Meter ‘n’ Temperature - Invalid Corrects or NC

Corrects Reset
2n49 Meter ‘n’ Temperature is in the Input or Output CR
Mode
2n50 Meter ‘n’ Temperature Signal is Suspect CR
2n51 Meter ‘n’ Body Fault - Over Temperature NC
2n52 Meter ‘n’ Critical Failure of SMV Electronics CR
2n53 Meter ‘n’ SMV Not Communicating CR
12 TB-980502 21/23/27.72+
HV Combo Module Address Jumpers

The HV Combo Module actually uses the same physical PCB module as a
regular H type combo module, except it uses a different address jumper setting.
Module Address
Jumpers
In ‘*’ Position
Green LED
Indicates Any
Activity
* * *
Red LED Indicates

OMNI is
Transmitting
SMV Channel #1
SMV Channel #2
Transmitter Loop
Status LEDs
SMV Channel #3
SMV Channel #4
Figure 1. Setting the Address Jumpers of the HV Combo Module
TB-980502 21/23/27.72+ 13
How the I/O Points are Assigned

When the flow computer detects that an ‘HV’ combo module is installed it
automatically allocates 12 of its 24 process inputs to the ‘HV’ module. The
presence or absence of combo modules is checked after a RESET ALL RAM or
after a CHECK I/O MODULES command is executed.
Although the ‘HV’ combo has only 4 physical Honeywell DE ports, each SMV-
3000 provides 3 variables for a total I/O requirement of 4 x 3 = 12. As the total
process input count of the flow computer is limited to 24 it is obvious that if an
‘HV’ combo module is fitted there can only be 3 other combo modules of type A,
B, E/D, E or H. The ‘HV’ combo module is always the last module in the list,
and the I/O assignments reflect this fact (see the following example).
Example 1: Omni 6000 - 2A - H1 – HV ( Flow computer contains - 2 ‘A’

combos, 1 ‘H’ combo, and an ‘HV’ combo).
st
Output points 1&2
nd
Output points 3&4
The ‘H’ combo is allocated: Input points 9, 10, 11 & 12

Output points 5&6
The ‘HV’ combo is allocated: Input points 13, 14, 15 & 16 Diff. Pressure
17, 18, 19 & 20 Temperature
21, 22, 23 & 24 Pressure
Output points 7&8
While the example shown above employs 4 combo modules in total, it uses all
24 process input assignments, this means that 2 physical I/O module slots will
be unusable on the backplane.
To configure an ‘HV’ combo module it is only necessary to configure the
Diff-Pressure I/O points in the Meter Run Config menu, the I/O points for the
temperature and pressure variables are automatically assigned by the flow
computer and cannot be changed by the user.
14 TB-980502 21/23/27.72+
Using the above example the following table identifies the I/O point assignments
that will occur.
available at: DIFFERENTIAL
TEMPERATURE PRESSURE
(281) 240-6161 PRESSURE
the WEB Page at: METER RUN # 1 13 17 21
www.omniflow.com
METER RUN # 2 14 18 22
or email to:
techsupport@omniflow.com METER RUN # 3 15 19 23
METER RUN # 4 16 20 24
Numbers in bold are entered by the user. Numbers in italics are assigned
automatically by the flow computer and cannot be changed.
OmniCom Revision
OmniCom revision ??.72 or later is required to support the SMV-3000
multivariable transmitter.
TB-980502 21/23/27.72+ 15
16 TB-980502 21/23/27.72+
Date: 02 28 06 Author(s): K. E. TB # 980503B
Serial I/O Modules: Installation Options
Contents
User Manual Reference Scope ................................................................................................................... 1
This technical bulletin Abstract ............................................................................................................... 1
complements the information
contained in Volume 1, and Features and Specifications .............................................................................. 2
is applicable to all firmware
revisions.
Dual Channel RS-232-C Serial I/O Module Model #68-6005............................ 3
RS-232-C / RS-485 Serial I/O Module Model #68-6205-A................................. 4
RS-232-C / RS-485 Serial I/O Module Model #68-6205-B................................. 6
RS-232-C / RS-485 Serial I/O Module Model #68-6205-F ................................. 7
RS-232-C / RS-485 Serial Port Jumper Options............................................... 9
Scope
All Omni 6000/3000 Flow Computers have serial communications capabilities
via proprietary serial I/O modules.
Getting Technical
Support
available at: Abstract
(281) 240-6161 Omni flow computers can come equipped with serial I/O modules that
Email should be sent via communicate with RS-232-Compatible or RS-485 devices. Omni manufactures
the WEB Page at:
three models of serial modules:
www.omniflow.com
or email to: Dual Channel RS-232-C Serial I/O Module Model # 68-6005
RS-232-C/RS-485 Serial I/O Module Model # 68-6205-A
RS-232-C/RS-485 Serial I/O Module Model # 68-6205-B
RS-232-C/RS-485 Serial I/O Module Model # 68-6205-F
Each serial module has 2 ports. Omni 6000 flow computers can have up to two
serial modules installed for a maximum of 4 ports. Omni 3000 flow computers
typically use one serial module providing 2 ports. Each serial communication
port is individually optically isolated for maximum common-mode and noise
rejection. Jumpers are provided for selection of module address and serial port
communication standards. Communication parameters such as protocol type,
baud rate, stop bits and parity settings are software selectable.

Features and Specifications

Proprietary serial modules and multi-bus serial I/O interface specifications are:
Omni Serial I/O Modules

MODEL # TYPE BASIC COMMUNICATION FEATURES
Dual channel serial communications
providing two RS-232-Compatible
Dual Channel RS-232- ports.
68-6005
Compatible Communications protocol, baud rate,
stop bits and parity settings are
software selectable.
Port #1 is factory-set as RS-232-
Compatible mode (jumper blocks are
soldered in place).
Port #2 is factory set to RS-485 mode.
RS-485 communications are jumper-
selectable as:
RS-232-Compatible / RS-485
68-6205-A
(Non-selectable Ports) ♦ 2-wire terminated or non-terminated
♦ 4-wire terminated or non-terminated
Communications protocol, baud rate,
Both Ports #1 and #2 are jumper-

selectable as either RS-232-C or RS-
485 modes.
RS-485 communications are jumper-
68-6205-B
RS-232-Compatible / RS-485 selectable as:
&
68-6205-F (Selectable Ports) ♦ 2-wire terminated or non-terminated
♦ 4-wire terminated or non-terminated
Communications protocol, baud rate,
INFO
Up to 12 flow computers Omni Multi-bus Serial I/O Interface

and/or other compatible
serial devices can be RS-232-COMPATIBLE RS-485
multi-dropped using Omni’s
proprietary RS-232- DATA OUTPUT VOLTAGE ±7.5 VOLTS (TYPICAL) 5 VOLTS (DIFFERENTIAL DRIVER)
Compatible serial port. LOAD IMPEDANCE 1.5 K OHM 120 OHM
Thirty-two devices may be
connected when using the SHORT CIRCUIT 10 MA (LIMITED) 20 MA
RS-485 mode. CURRENT
Typically, one serial I/O INPUT LOW THRESHOLD -3.0 VOLTS 0.8 VOLTS (DIFFERENTIAL INPUT)
module is used on the Omni INPUT HIGH THRESHOLD +3.0 VOLTS 5.0 VOLTS (DIFFERENTIAL INPUT)
3000, providing two ports. A
maximum of two serial BAUD RATES 1.2, 2.4, 4.8, 9.6, 19.2, & 38.4 K BPS (SOFTWARE SELECTABLE)
modules can be installed in COMMON MODE ±250 VOLTS TO CHASSIS GROUND
the Omni 6000, providing VOLTAGE
four ports.
LEDS CHANNEL INPUTS/OUTPUTS & HANDSHAKING SIGNALS
2 TB-980503B ALL REVS

TB-980503 Serial I/O Module: Installation Options
Dual Channel RS-232-C Serial I/O Module

Model #68-6005
Note: Dual channel serial communication modules can be installed providing two RS-
Up to 12 flow computers 232-Compatible ports. Although providing RS-232-C signal levels, the tristate
and/or other compatible serial output design allows multiple flow computers to share one RS-232 device. This
devices can be multi-dropped serial module is the oldest model manufactured by Omni.
using Omni’s proprietary RS-
232-C serial port.
Typically, one serial I/O
module is used on the Omni
3000, providing two ports. A
maximum of two serial
modules can be installed in the
Omni 6000, providing four
ports.
Address Selection
Jumpers
Jumper Settings:
Address S1 (1)
For information on setting
the jumpers of serial I/O 1 Selected for Serial
modules refer to 1.6.3. Ports 1 & 2
“Serial Communication
Modules” in Volume 1,
Chapter 1 of the User
Manual. Address S2 (0)
Selected for Serial
0
Ports 3 & 4
RTS Out
Chan. B
TX Out
RTS Out
Chan. A
TX Out
LED Indicators
RX In
Chan. A
RDY In
RX In
Chan. B
RDY In
Fig. 1. Dual RS-232 Serial I/O Module Model Showing Selection Jumper
and Indicator LEDs
TB-980503B ALL REVS 3

RS-232-C / RS-485 Serial I/O Module Model

Note:
#68-6205-A
Serial I/O Module # 68-6205-A (manufactured 1997) has two communication
Up to 12 flow computers ports. The first serial port (Ports #1 and #3 if two 68-6205 modules are installed)
and/or other compatible is factory set in the RS-232-C mode (jumpers are soldered into place and
serial devices can be multi- cannot be moved). The second serial port (Ports #2 and #4) is configurable for
dropped using Omni’s
proprietary RS-232-C serial RS-485 communications only. Although the first serial port provides RS-232-C
port. Up to 32 devices may signal levels, the tristate output design allows multiple flow computers to share
be connected when using one serial link.
the RS-485 mode. Refer to
technical bulletin TB980401
“Peer-to-Peer Basics” for
more information. Address Selection
Typically, one serial I/O Jumpers
module is used on the Omni Address S3 Selected
3000, providing two ports. A for Serial Ports 5 & 6
Address S1 Selected
maximum of three serial for Serial Ports 1 & 2
modules can be installed in
the Omni 6000, providing
six ports. Address S2 Selected
for Serial Ports 3 & 4
Jumper Settings
IRQ Select Jumper
For information on setting
the jumpers of serial I/O IRQ 2 Selected
modules refer to 1.6.3. (If using an SV
“Serial Communication Module, select
Modules” in Volume 1, IRQ 3)
Manual. For serial port
jumper settings see also
Fig. 6 in this bulletin.
LED Indicators
68-6205 REV: A
Port #2 (#4) (#6) Port #1 (#3) (#5) Jumpers

Jumpers (Hard-wired to RS-232-C Only)
Fig. 2. RS-232/485 Module #68-6205-A Showing Selection Jumpers and

Indicator LEDs

The first serial port jumpers are factory hard-wired for RS-232-C mode. This port
is non-selectable and cannot be changed by the user. The second serial port
jumpers are factory preset in the RS-485 two-wire, terminated positions. This
port is user-selectable for RS-485 two-wire/four-wire terminated/non-terminated
jumper positions (see Fig. 6). Back panel wiring is shown below.
Micro Motion™ RFT
9739 Devices
Users of Micro Motion™

RFT 9739 devices
connected to the peer-to-
peer port (Port #2) of the
Omni, please note that the
resistor networks should be
positioned for 2-wire RS-
485 and that Terminal A
from the RFT 9739 should
be wired to Omni Terminal Omni 6000
B (7), and B from the RFT (Omni 3000)
must be wired to Omni
Terminal A (11). Refer to Terminal RS-485 RS-485
RS-232-C
technical bulletin TB3 (TB2) 2-Wire 4-Wire
TB980401 “Peer-to-Peer
Basics” for more 1 TX
information.
2 TERM
First 3 RX RS-232-C
Serial
Port 4 GND Hard-wired
5 RTS
6 RDY
7 B TX-B
8 ⎯ ⎯
Second 9 ⎯ RX-B
Serial N/A
Port 10 GND GND
11 A TX-A
12 ⎯ RX-A
Fig. 3. Back Panel Wiring of the RS-232-C/RS-485 Module #68-6205-A


#68-6205-B
INFO Serial I/O Module # 68-6205-B is the latest serial module manufactured by Omni
(1998). It is capable of handling two communication ports. Each serial port is
Up to 12 flow computers jumper-selectable for either RS-232-Compatible or RS-485 communications.
serial devices can be multi- Although providing RS-232-C signal levels when in this mode, the tristate output
dropped using Omni’s design allows multiple flow computers to share one serial link. In addition to the
proprietary RS-232-C serial RS-232 mode, jumper selections have been provided on each port to allow
port. Up to 32 devices may
selection of RS-485 format. With this option, a total of two RS-485 ports are
be connected when using
the RS-485 mode. Refer to available on this model.
more information. Ad d ress S electio n
Typically, one serial I/O Ju m p ers
module is used on the Omni Address S 3 S elected
3000, providing two ports. A for S erial Ports 5 & 6
Address S 1 S elected
maximum of two serial for S erial Ports 1 & 2
four ports. Address S 2 S elected
for S erial Ports 3 & 4
Jumper Settings IR Q S elect Ju m p er
For information on setting IR Q 2 S elected

the jumpers of serial I/O (If using an S V
modules refer to 1.6.3. M odule, select
“Serial Communication IR Q 3)
Fig. 6 in this bulletin. L E D In d icato rs
68-6205 R EV: A
P o rt #2 (#4) Ju m p ers P o rt #1 (#3) Ju m p ers

(R S -485 Options Only ) (Hard-wired to R S -232-C Only )
Fig. 4. RS-232-C/RS-485 Module #68-6205-B Showing Selection Jumpers

and Indicator LEDs


#68-6205-F
INFO Serial I/O Module # 68-6205-F is the latest serial module manufactured by Omni
(2000). It is capable of handling two communication ports. Each serial port is
Up to 12 flow computers jumper-selectable for either RS-232-Compatible or RS-485 communications.
serial devices can be multi- Although providing RS-232-C signal levels when in this mode, the tristate output
dropped using Omni’s design allows multiple flow computers to share one serial link. In addition to the
proprietary RS-232-C serial RS-232 mode, jumper selections have been provided on each port to allow
port. Up to 32 devices may
selection of RS-485 format. With this option, a total of two RS-485 ports are
be connected when using
the RS-485 mode. Refer to available on this model.
more information. Ad d ress S electio n
Typically, one serial I/O Ju m p ers
module is used on the Omni Address S 3 S elected
3000, providing two ports. A for S erial Ports 5 & 6
Address S 1 S elected
S2
S1
maximum of two serial
S2
S1
S2
S1
four ports. Address S 2 S elected
Jumper Settings IR Q S elect Ju m p er
For information on setting IR Q 2 S elected

the jumpers of serial I/O (If using an S V
0
1
modules refer to 1.6.3.

S2
S1
M odule, select
“Serial Communication IR Q 3)
IRQ

Fig. 6 in this bulletin. L E D In d icato rs
68-6205 R EV: F
P o rt #2 (#4) Ju m p ers P o rt #1 (#3) Ju m p ers

(R S -485 Options Only ) (Hard-wired to R S -232-C Only )
Fig. 5. RS-232-C/RS-485 Module #68-6205-B Showing Selection Jumpers

and Indicator LEDs

Jumpers for both serial ports are user-selectable to RS-232-C or RS-485

formats (see Fig. 6). The RS-485 options are either 2-wire or 4-wire mode; each
mode can be set as terminated or non-terminated connections. Back panel
wiring is shown below.
Micro Motion™ RFT
9739 Devices
Users of Micro Motion™

RFT 9739 devices
connected to the peer-to-
peer port (Port #2) of the
Omni, please note that the
resistor networks should
be positioned for 2-wire
RS-485 and that Terminal
A from the RFT 9739
should be wired to Omni Omni 6000
Terminal B (7), and B from (Omni 3000)
the RFT must be wired to
Omni Terminal A (11). Terminal RS-485 RS-485
RS-232-C
Refer to technical bulletin TB3 (TB2) 2-Wire 4-Wire
TB980401 “Peer-to-Peer
Basics” for more 1 TX B TX-B
information.
2 TERM ⎯ ⎯
First 3 RX ⎯ RX-B
Serial
Port 4 GND GND GND
5 RTS A TX-A
6 RDY ⎯ RX-A
7 TX B TX-B
8 TERM ⎯ ⎯
Second 9 RX ⎯ RX-B
Serial
Port 10 GND GND GND
11 RTS A TX-A
12 RDY ⎯ RX-A
Fig. 6. Back Panel Wiring of the RS-232-C/RS-485 Module #68-6205-B

RS-232-C / RS-485 Serial Port Jumper Options

Serial Port I/O Software The RS-232-C/RS-485 serial port has been designed so that RS-232 or RS-485
Settings communications standards can be selected by placement of 16-pin resistor
networks into the correct blocks. The following diagrams show the locations of
Each serial port is blocks JB4, JB5, JB6 for the first serial port (Model #68-6205-B only), and JB1,
configurable via JB2, JB3 for the second serial port (Models #68-6205-A and #68-6205-B) for
OmniCom® software or the each format. Serial I/O Module #68-6205-A only has the RS-485 options
Omni front panel. Detailed available for the second serial port, and the first port is hard-wired to the RS-
information on how to
configure these and other 232-C position and cannot be changed by the user.
flow computer settings is
available in Volume 3,
Manual and in OmniCom
Help. RS-232
JB1 or JB4 JB2 or JB5 JB3 or JB6
RS-485 RS-485 2-WIRE
RS-485
TERMINATED
RS-485 2-WIRE TERMINATED RS-485 2-WIRE NON-TERMINATED

JB1 or JB4 JB2 or JB5 JB3 or JB6 JB1 or JB4 JB2 or JB5 JB3 or JB6
RS-232/485
NON-TERMINATED
RS-485
Terminated/Non- RS-232 RS-232/485 4-WIRE RS-232 RS-232/485 4-WIRE
TERMINATED
terminated RS-485
The RS-485 devices located

at each extreme end of an
RS-485 run should be
terminated. Note that the
device located at an extreme RS-485 4-WIRE TERMINATED RS-485 4-WIRE NON-TERMINATED
end may or may not be an JB1 or JB4 JB2 or JB5 JB3 or JB6 JB1 or JB4 JB2 or JB5 JB3 or JB6
Omni Flow Computer.
RS-232/485
RS-485 2-WIRE NON-TERMINATED RS-485 2-WIRE
RS-232 RS-485
RS-232 TERMINATED
Fig. 7. Layout of Jumper Blocks Showing RS-232/485 Formats

Multivariable Flow Transmitter Interfaces:

Connectivity and Data Transfer Issues
Contents
complements the information
contained in the User Improving Accuracy and Performance............................................................. 2
Manual, applicable to all Multiple Sensors and Parameters ................................................................................. 2
revision .72+.
Scan Interval ................................................................................................................. 2
Time Lag ....................................................................................................................... 2
Multivariable Flow
Transmitters Transferring Flow Rate and Totalizer Data ...................................................... 3
These are a special type of Serial Data Communications ............................................................................. 4
smart digital instrumentation The Flowmeter Device as a Communication Slave ....................................................... 4
device that incorporates
multiple sensors. The sensors The Flowmeter Device as a Communication Pseudo Master ........................................ 4
are controlled by The Flowmeter Device as a Full Communication Master .............................................. 4
microprocessors. Point-to-Point Configurations......................................................................................... 5
Advantages and Disadvantages of a Serial Data Link................................................... 6
Direct Pulse Train ............................................................................................... 7
Scope
This technical bulletin applies to all firmware revisions versions .72+ of Omni
6000/Omni 3000 Flow Computers.
Abstract
The term ‘multivariable flow transmitter’ denominates a class of smart digital
instrumentation devices. This class of device incorporates multiple sensors
controlled by either one or more microprocessors. Coriolis and ultrasonic liquid
and gas flowmeters are examples of current multivariable transmitter
technology. These devices use some form of serial data communication link to
transfer data to and from the Omni flow computer, requiring an ‘SV’ multivariable
communication combo module. In addition, the devices provide an output pulse
train which is proportional to the flow (either mass or volume).
TB-980504 ALL.72+ 1
Improving Accuracy and Performance

Obtaining high accuracy is the primary goal of instrumentation designers. The
inclusion of one or more microprocessors gives the instrument designer the
ability to improve the performance of a device, by taking advantage of the fact
that the measurement sensor is far more repeatable than it is accurate. For
example, given the same set of operating conditions, the sensor is able to
reproduce its results in an extremely predictable manner within the range of its
sensors. At a different set of operating conditions, the sensor results may be
different but still extremely predictable.
Some considerations for improving measurement accuracy and instrument
performance are the use of multiple secondary sensors and parameters, and
the device’s scan interval and the time lag it produces to calculate results from a
sensor measurement.
Multiple Sensors and Parameters

The microprocessor allows the manufacture to characterize and correct the
measurement sensor results by monitoring its electronic ambient conditions and
sensor operating conditions. This is done using secondary sensors or
calculating parameters such as temperature, pressure and density. The net
result is greatly improved accuracy of the measurement output, and the
availability of other measured or calculated parameters, which can be used by
tertiary devices such as flow computers. The flow computer uses these
parameters as values for input variables in ‘equations of state’ and to diagnose
the condition of the transmitter.
Scan Interval
All microprocessor controlled multivariable flowmeter devices operate on some
scan interval; i.e., input parameters are measured on a scan interval (fixed or
variable). The measured parameters are then input into a calculation sequence
which produces a resultant flow rate, (either mass / unit time or volume / unit
time).
Time Lag
Note that sensor measurements must be taken before a result can be
calculated. The calculated flow rate represents that which existed for the
previous scan interval; i.e., there is a time lag from when the measurement is
taken to when the flow rate is calculated. Fast scan intervals are typically used
to minimize any uncertainty that may be introduced by this time lag.
2 TB-980504 ALL.72+
TB-980504 MV Flow Transmitter Interfaces: Serial Connectivity vs. Direct Pulse Trains
Note Transferring Flow Rate and Totalizer Data

At the time that this bulletin alarms which can be of great benefit to the user. This data could be processed
was being prepared, certain and used to warn the user of impending failures or operational problems before
manufacturers were making they have had a major impact on the uncertainty of the measurement result.
firmware adjustments to
their products to provide
There is no question that the integrity of the measurement is greatly enhanced
high resolution totalizers by providing this data to the flow computer and allowing the flow computer to log
suitable for use by the Omni and alarm any abnormalities detected.
flow computer.
Various multivariable flowmeter devices update their database with the most
recently calculated volume or mass flow rate. The Omni flow computer, which is
operating on a 500 msec calculation cycle, uses the last flow rate received from
the flowmeter to calculate the incremental flow quantity for the current
calculation cycle.
Most flowmeter devices also provide internal totalizers. Using these totalizers
can be difficult unless they are provided in a numeric format which increments
and rolls over predictably. Floating point variables for example normally keep
increasing in value and do not roll over to zero at any point. This causes a
problem because as the totalizer increases in size, a point is reached when the
bit resolution of the mantissa portion of the number is exceeded, and the
totalizer begins to increment using larger and larger steps. The flow computer
could compare the totalizer values received between successive serial
transmissions, but because of the totalizer roll over and resolution problems,
and the inability to synchronize the reading of successive totalizer readings with
the calculation cycle of the flow computer, it is better to use the instantaneous
flow rate value obtained via a direct connection to calculate and totalize the flow
in the flow computer. This has significance because it forms the basis for the
totalizer integration within the transmitter.
TB-980504 ALL.72+ 3
Serial Data Communications

Each time the device performs its measurement scan and calculation process, it
typically updates the values of calculated variables, measured parameters and
alarm points in its database. Some flowmeter devices act as ‘serial
communication slaves’, allowing the database to be asynchronously read and,
in some cases, modified. Other devices act as ‘serial communication pseudo
masters’ and simply transmit certain database points on a regular time interval,
while acting as a slave and accepting commands and configuration changes. At
least one device the Krohne Ultrasonic flowmeter can be both ‘full
Getting Technical communication master’ and ‘communication slave’.
Support
available at: The Flowmeter Device as a Communication Slave
(281) 240-6161
Email should be sent via In this mode the flowmeter device transmits data as requested by the flow
the WEB Page at: computer communication master. When asked for data, the flowmeter will
www.omniflow.com transmit the most recently calculated data or block of data. In normal operation,
or email to: the flow computer requests flow and diagnostic data on a regular interval and
techsupport@omniflow.com intersperses any other data transmissions (e.g., configuration data or
commands) between these regular flow update polls. Sometimes due to heavy
communications traffic, communication glitches or transmission retries, flow
update polls can be time-skewed or missed altogether.
The Flowmeter Device as a Communication Pseudo

Master
In this mode a fixed block of data is transmitted over and over on a regular
interval without requiring a response, (e.g., Instromet ultrasonic gas flowmeter
transmits a information data block every second). Any command or
configuration data that is needed to be sent to the flowmeter transmitter must be
interspersed between these regular data block transmissions. It is the job of the
flow computer acting as communication master to ensure that configuration
changes do not collide with information data block transmissions. Sometimes
due to flow computer task loading, communication glitches or transmission
retries, flow data blocks can be time-skewed.
The Flowmeter Device as a Full Communication Master

The Krohne ultrasonic flowmeter can be configured to act as a Modbus master.
In this mode the flowmeter can be configured to realize transactions of up to 20
predefined data blocks, which can be writes of data to a flow computer or reads
of data from a flow computer. Each transaction requires a response from the
slave flow computer. Update cycle time can be excessive if too many blocks
with too much data are transferred and, as with the other serial communication
methods, glitches and transmission retries can delay or time-skew the data
received.
4 TB-980504 ALL.72+
Point-to-Point Configurations
Point-to-point configurations (Fig. 1), with both the flow computer and
transmitter terminated, is the only acceptable wiring configuration.. Each
flowmeter transmitter is connected to an independent ‘SV’ port of the flow
computer. Because each ‘SV’ port is connected to only one flowmeter
transmitter, each transmitter can now use a default communication address of
‘1’, greatly simplifying flow transmitter replacement issues. Data transfers are
much faster then in a multi-drop mode and the likelihood of transmitter
interaction is greatly minimized.
All 4 MV Ports of Multivariable Multivariable Multivariable Multivariable

Flow Computer Device Device Device Device
must be Terminated ID #1 ID #2 ID #3 ID #1
Omni Flow
Computer
(Using
Independent
SV Ports)
Modbus IDs of Multivariable All Four Multivariable
Devices can be the same in this Devices must be
Point-to-Point Configuration Terminated
TB-980504 ALL.72+ 5
Advantages and Disadvantages of a Serial Data Link

The advantages of totalizing the flow in the flow computer using data obtained
via a serial data link are:
• Saving of two wires needed to transmit the pulse signal
• No need to setup the multivariable flowmeter to output a pulse signal
Disadvantages of totalizing the flow in the flow computer using data obtained via
a serial data link are:
• High level of instrumentation and technical expertise needed to maintain
and debug an installation; e.g., the average metering technician is
unlikely to be familiar with serial communication protocols, or able to
operate a serial data protocol analyzer needed to interpret the data
messages received from the flowmeter.
• A cyclic or rapid change in flow rate at the flowmeter may not be
captured correctly because of the relatively slow scan rate of the serial
transmission link.
• The flow rate update rate cannot be guaranteed to be regular in some
cases due to communication glitches requiring communication retries
and time-outs. Other factors which affect this are intermittent
configuration and calibration transactions which may occur on the serial
link. (these concerns are multiplied in a multi-dropped wiring system).
6 TB-980504 ALL.72+
Direct Pulse Train

From the calculated flow rate obtained from each measurement scan, the
device calculates and outputs a pulse train of a certain frequency via a digital
output. Each pulse will represent an exact amount of incremental flow. In some
cases, a second digital output can be used to provide an exact copy of the pulse
train except that it will be out of phase with the original pulse. These two pulse
trains approximate the type of pulse output that is received from a dual pickoff
turbine meter and as such can satisfy many of the ‘Pulse Fidelity’ checking
requirements expressed in API MPMS, Chapter 5.5. The flow computer counts
each and every pulse output by the flowmeter device and applies a flowmeter K-
Factor as it would for any other pulse producing flowmeter. K-factors can be
either in pulses per mass unit or pulses per volume unit. Changes in flow rate
are immediately reflected in the pulse output and registered by the flow
computer, within the cycle update limitations of both devices.
The advantages of totalizing the flow in the flow computer via a direct pulse
train are:
• Flowmeter response time is as fast as the measurement and calculation
scan period; e.g., a sudden increase or loss of flow would be detected
within one calculation cycle.
• Individual device scan cycles have no impact on uncertainty. Signal
aliasing is not a problem.
• Easy to implement ‘Dual Pulse Fidelity Checking’ using a second out of
phase pulse using existing flow computer technology.
• Low level of instrumentation and technical expertise needed to maintain
and debug an installation; e.g., a metering technician with simple digital
counter is all that is required to verify proper operation.
• Ability to prove the device using conventional pipe provers and compact
provers (applying double chronometry pulse interpolation methods).
Disadvantages of totalizing the flow in the flow computer via direct pulse train
are:
• Two extra wires are needed to transmit the pulse signal.
• Need to configure (scale) the digital I/O point pulse train frequency.
TB-980504 ALL.72+ 7
8 TB-980504 ALL.72+
Date: 05 28 03 Author(s): T.J. T. / R. S. TB # 980701
Using the Totalizer Maintenance Mode
Contents
This technical bulletin is Abstract ............................................................................................................... 1
applicable to Revisions
24.72+ and 23.73+ for Procedure to Start and End Maintenance Mode.............................................. 2
metric units only.
Displaying the Maintenance Totals................................................................... 3
Totalizer Maintenance Totalizers ............................................................................................................. 3
Mode Status ................................................................................................................... 3
This mode allows the Maintenance Mode Command ........................................................................... 4
operator to verify meter run
calculations by measuring Modbus Database Points Associated with the Totalizer Maintenance
meter run flow rate (gross, Mode..................................................................................................................... 4
net, mass, or energy)
without impacting the
custody transfer totals.
Scope
The Maintenance Mode feature applies to the following application revisions:
24.72+ Turbine / Positive Displacement / Coriolis Liquid Flow Metering
Systems with K Factor Linearization (metric units only)
23.73+/27.72+ Office/Turbine Gas Flow Metering System
Abstract
The purpose of maintenance mode function is to allow operators to verify meter
run calculations. This function measures meter run flow rate (gross, net, mass,
and energy) without impacting the overall operation of the custody transfer
totals.
When in the maintenance mode, the flow measured by the target meter run will
not be accumulated in the meter run and/or station totalizers used for normal
operation. Furthermore, any D/A outputs configured to output flow rate will not
be impacted. While the specific meter is in the maintenance mode, the meter will
display zero flow in all the non-maintenance mode displays.
TB-980701 24/26/27.72+ 1
Procedure to Start and End Maintenance Mode

The maintenance mode function requires a technician Level '1' password.
Following is the required procedure to Start and End the Maintenance Mode:
(1) Enter a positive value for ‘low flow cutoff’ or ‘active frequency’ (see
“Meter Run Setup” in Chapter 3 of the User Manual). A positive entry
must be made to ensure that the meter active flag operates correctly at
zero flow.
(2) Shutdown the meter (flow rate = Zero).
Maintenance Mode (3) In the display mode, press [Alpha Shift] [Prog] [Meter] [n] [Enter]. The
Active/Inactive Omni LCD screen will display:
If there is a ‘Y’ next to
‘Maintenance Mode’ in the
display (see right), then the METER #1 MAINTENANCE
mode is active. The Maintenance Mode N
maintenance mode is Reset Maint Totals
inactive when an ‘N’ is Toggle Maint Mode _
displayed.
(4) Press [ ] (down arrow key) to place the cursor at ‘Toggle Maint Mode’
and press [Alpha Shift] [Y] [Enter]. Depending on the maintenance
mode status, the Omni will toggle the mode. If the maintenance mode is
Configuration Settings active, then this step will end or “turn off” the mode; and vice versa.
The maintenance mode You will be prompted for the password. The LCD screen will display:
uses current flow computer
configuration settings; i.e.,
additional configuration METER #1 MAINTENANCE
entries are not required Maintenance Mode N
Reset Maint Totals
Password _
INFO (5) Type the Level 1 password and press [Enter]. The Omni LCD screen will
display a screen similar to the following:
When the maintenance
mode starts after selecting
the type of measurement METER #1 MAINTENANCE
(gross, net, mass or
energy), the flow rate and Maintenance Mode Y
totalized flow are zero. Reset Maint Totals
Toggle Maint Mode _
(6) To end (deactivate) the totalizer maintenance mode, repeat steps (2)
through (5).
2 TB-980701 24/26/27.72+
TB-980701 Using the Totalizer Maintenance Mode
Displaying the Maintenance Totals

In the display mode, select the displays you want by entering the corresponding
INFO keypress sequence:
Pressing [Gross] [Enter] in ❑ For Gross Flow Maintenance Totals, press [Meter] [n] [Gross].
the maintenance mode will
display the station and ❑ For Net Flow Maintenance Totals, press [Meter] [n] [Net].
meter flow for this mode.
❑ For Mass Flow Maintenance Totals, press [Meter] [n] [Mass].
❑ For Energy Flow Maintenance Totals (gas applications only Revision
27.72+), press [Meter] [n] [Energy].
The Omni LCD screen will display:
MaintenanceMode am3h
Current Flow Rate Meter Tag 0.000
MaintenanceMode am3
Totalized Value
Meter Tag 0.000
Meter Run Database Totalizers

Registers
In the totalizer maintenance mode, the flow computer will realize all normal
The “n” in the database
point number represents the calculations and accumulate resulting flow quantities into special maintenance
meter run number (n = 1, 2, totalizers. The special totalizer registers reset to zero upon entry to maintenance
3 or 4). mode or can be manually reset while in the maintenance mode. This reset will
not affect the regular meter run totalizers. In this mode, the LCD screen will
display meter run current flow rate and accumulated flow rate for the
maintenance mode. Following are the Modbus database registers assigned as
special maintenance mode totalizers:
5n92 Gross Maintenance Total
5n93 Net Maintenance Total
5n94 Mass Maintenance Total
5n95 Energy (NSV) Maintenance Total
Status
The following status points are provided in the Omni flow computer’s Modbus
database to indicate when a meter run is in the totalizer maintenance mode:
1197 Meter Run #1 - Maintenance Mode Status
TB-980701 24/26/27.72+ 3
Maintenance Mode Command

The maintenance mode function can be activated/deactivated remotely,
providing that the flow rate is zero and the meter run is inactive (1n05 = 0). The
meter run totalizer maintenance mode is activated by setting one or all the
following Modbus database points to '1'; the mode will be ended by writing '0' to
these same database points.
2737 Meter Run #1 - Toggle Maintenance Mode Command
Modbus Database Points Associated with the

Totalizer Maintenance Mode
The following table comprises the database registers for the maintenance mode
function:
MODBUS DATABASE POINTS ASSOCIATED WITH THE MAINTENANCE MODE

Database Point Number
Database Point Description Meter #1 Meter #2 Meter #3 Meter #4

Meter Run Maintenance Mode Status 1197 1297 1397 1497
Gross Maintenance Mode Totalizers 5192 5292 5392 5492
Net Maintenance Mode Totalizers 5193 5293 5393 5493
Mass Maintenance Mode Totalizers 5194 5294 5394 5494
Energy (NSV) Maintenance Mode Totalizers 5195 5295 5395 5495
Maintenance Mode Command 2737 2738 2739 2740
4 TB-980701 24/26/27.72+
Date: 05 28 03 Author(s): R. S. TB # 980801
Unsolicited Transmissions of Custom

Modbus Data Packets
Contents
Scope ...................................................................................................................1
User Manual Reference
Abstract................................................................................................................2
complements the Custom Modbus Data Packets ....................................................................... 2
User Manual, specifically Prerequisites for Using Unsolicited Transmissions of Custom Data
Volume 3, Chapter 4 Packets ................................................................................................................ 2
“Modbus Protocol
Implementation”, and is User-customized Modbus Driver ................................................................................... 2
applicable to all revisions Compatible Serial Communications .............................................................................. 3
.71+.
Modbus Protocol Implementation of Omni Proprietary Function
Code 67: Transmit Read Unsolicited Custom Data Packet ............................ 3
Unsolicited Configuring Your Flow Computer for Unsolicited Transmissions of
Transmissions Custom Data Packets ......................................................................................... 4
These type of transmissions Example ........................................................................................................................ 4
are used for Omni flow
computers to transmit
custom data packets via an
RS-232-C serial port without
Scope
a poll. This feature is
especially useful when
communicating via VSAT
satellite systems. Modbus This technical bulletin applies to all firmware revisions versions .71+ of Omni
protocol Function Code 67 6000/Omni 3000 Flow Computers.
has been assigned to this
function exclusively for
Omni flow computers.
TB-980801 ALL.71+ 1
Abstract
Unsolicited transmissions are used to transmit a ‘Custom Modbus Data Packet’
from a selected flow computer RS-232-C serial port without it being polled for
data by the receiving device. Modbus protocol Function Code 67 was assigned
for this feature, which allows the receiving device to discriminate between a
transmission without a poll (unsolicited) and a normal Modbus read.
This function, among other uses, was designed for communicating via VSAT
satellite systems where operating cost is directly proportional to RF bandwidth
used. In communications via satellite, polled transmissions are much more
costly than unsolicited transmissions. Typically, the device requesting data
(master) would poll the flow computer to transmit the data to it through a satellite
link. This would require a signal from the master device to the flow computer
and yet another from the flow computer back to the requesting device. Whereas
with unsolicited transmissions, the flow computer can be configured to transmit
Modbus custom data packets at specified time intervals, when a certain event
occurs, or by some other transmission triggering cause, without the master
device having to poll the flow computer for such data. In this manner, only one
signal is transmitted via satellite; i.e., from the flow computer to the master
device.
Custom Modbus
Data Packets Custom Modbus Data Packets
Many point numbers were Custom Modbus Data Packets are provided to reduce the number of polls
left unused when
numbering the variables needed to read multiple variables which may be in different areas of the
within the database. This database. Groups of consecutive database points of any type of data can be
allows for future growth joined together into one packet by entering each data group’s starting database
and different application index number. The number of data bytes in a custom packet which will be used
data. Without custom data
packets many polls would for unsolicited transmissions cannot exceed 248 in RTU mode or 496 in ASCII
be required to retrieve data mode.
distributed throughout the
database. The custom data
Prerequisites for Using Unsolicited

packets allows you to
concatenate or join
Transmissions of Custom Data Packets

different groups or sets of
data in any order and of
any data type into 1
message response. These Before you can configure your flow computer to realize unsolicited
custom packets are transmissions of custom Modbus data packets, you must have the following:
located at points 0001,
0201 and 0401 in the ❑ User-customized Modbus driver for receiving device
database.
For more information refer ❑ Compatible serial communications capability
to 2.5.18 and 4.6 in
Volume 3, and 1.1, 1.3.14
and 2.1 in Volume 4 of the
User Manual.
User-customized Modbus Driver
Various communication master devices can be connected to the Omni flow
computer via Modbus serial link including, but not limited to, front-end
supervisory control and data acquisition (SCADA) system devices. In order for
these devices to be able to identify and read unsolicited transmissions of Omni
flow computer custom data packets, the user must develop a custom driver
capable of identifying the Modbus protocol Function Code 67; which is an Omni
proprietary function. The custom driver must then be installed in the SCADA or
other receiving device and verified for adequate performance.
2 TB-980801 ALL.71+
TB-980801 Unsolicited Transmissions of Custom Modbus Data Packets
Compatible Serial Communications

Both the Omni flow computer and the receiving device must be equipped with
appropriate RS-232 compatible or RS-485 serial ports configured for Modbus
protocol implementation. The Omni flow computer has several hardware and
software options for RS-232 or RS-485 compatible serial data links (refer to the
User Manual for details).
Modbus Protocol Implementation of Omni

Proprietary Function Code 67: Transmit
Unsolicited Custom Data Packet
A typical unsolicited transmission Modbus protocol message format using
Function Code 67 is as follows:
Modbus Protocol Message Format using Function Code 67
CUSTOM
DEVICE FUNCTION BYTE CRC ERROR
PACKET DATA
ADDRESS CODE 67 COUNT CHECK BYTES
ADDRESS
XX 43HEX XX XXXXHEX DD DD ... DD DD CRC CRC
Device Address : The address that identifies the Omni flow

computer that is transmitting unsolicited
data.
Function Code 67 : Represented in hexadecimal value as 43.
Byte Count : The number of bytes of the data field
(maximum of 248 bytes in RTU mode or 496
bytes in ASCII mode).
Custom Packet Address : The flow computer database address of the
custom Modbus data packet, represented in
hexadecimal value:
Custom Modbus Data Packet Addresses
Hexadecimal Equivalents
PACKET PACKET HEXADECIMAL
NUMBER ADDRESS EQUIVALENT
#1 0001 0001
#2 0201 00C9
#3 0401 0191
Data : The actual flow computer data transmitted

without a poll to the receiving device.
CRC Error Check Bytes : Used to check the message for errors.
For more information on Modbus protocol implementation, see Chapter 4 in

Volume 3 of the User Manual.
TB-980801 ALL.71+ 3
Configuring Your Flow Computer for

Unsolicited Transmissions of Custom Data
Packets
User-programmable To activate unsolicited transmissions you must enable any of the following ‘edge
Boolean Statements triggered’ command points below which causes the appropriate custom Modbus
and Variables data packet’ to be transmitted out of the selected serial port without the serial
For more information, see port being polled for data:
Volume 4 for addresses of
Boolean statements and
user-programmable Flow Computer Modbus Database Points for
variables, and Chapter 2 in Unsolicited Transmissions
Volume 3 on configuring
Boolean statements and ADDRESS UNSOLICITED TRANSMISSION TYPE
user-programmable
variables. 2701 Custom Data Packet #1 via Serial Port #1
2702 Custom Data Packet #2 via Serial Port #1
Example
The following user-programmable variables are an example of programming a
timer for every 15 seconds which triggers the unsolicited transmission of a
custom Modbus data packet.
7025: 7026 ) 7026 = # -15

7026: 7026 + # 0.5
The following Boolean statement is an example of an unsolicited transmission

where every 15 seconds the data contained in Custom Modbus Data Packet #3
will be transmitted without a poll via the flow computer’s Serial Port #2 to the
receiving device:
1025: 2706 = 7026
4 TB-980801 ALL.71+
Last Updated: 05 29 2003 TB # 980802
Digital I/O Modules: Installation Options
Contents
Scope ................................................................................................................... 1
Abstract ............................................................................................................... 1
Installation Options and Jumper Settings ....................................................... 2
Digital I/O Module Model # 68-6011 .............................................................................. 2
Digital I/O Module Model # 68-6211 .............................................................................. 3
User Manual Reference Scope

complements the
All Omni 6000/3000 Flow Computers have digital I/O capabilities via proprietary
information contained in digital I/O modules.
Volume 1, and is applicable
to all firmware revisions.
Abstract
Omni flow computers have digital I/O module options with user-selectable
jumpers for module address, sequence and interrupt request (IRQ). Omni
manufactures two models of digital modules:
❑ Digital I/O Module Model # 68-6011

❑ Digital I/O Module Model # 68-6211
Each digital module has 12 digital points. Each digital point can be individually
configured as either an input or an output, via the front panel keypad or a serial
port using OmniCom configuration PC software.
TB-980802 ALL.71+ 1
Installation Options and Jumper Settings

Only 1 digital I/O module can be installed in the Omni 3000 and a maximum of 2
installed in the Omni 6000. This provides a total of 12 digital I/O points for the
Omni 3000 and a total of 24 digital I/O for the Omni 6000.
Digital I/O Module Model # 68-6011

Inputs and outputs are provided for control of prover functions, remote totalizing,
I/O Point LEDs sampler operation, tube control, injection pump control, and other miscellaneous
functions. Each digital I/O module provides a total of 12 digital I/O points. Each
Each digital I/O point has 2
LEDs (green and dual point can be configured independently as an input or output. Points are
red/green) which indicate its individually fused and include LEDs indicating that the point is active and if the
status. When the single fuse is blown. The digital I/O module normally occupies I/O Slots 1 and 2 on the
green LED is glowing, the
digital I/O point is active.
Omni 6000 backplane, and I/O Slot 1 on Omni 3000. User-selectable jumper
The dual red/green LED settings are shown in Figure 1 (below):
indicates a blown fuse, red
indicating a source current
and green a sinking current.
JP1 In = Dig. 1 Rising Edge Trigger

Interrupt Request (IRQ) JP2 In = Dig. 1 Falling Edge Trigger
Select Jumpers for JP3 In = Dig. 2 Rising Edge Trigger
Pipe Prover Detector JP4 In = Dig. 2 Falling Edge Trigger
(Non-Double Chronometry)
NOTE: If “D2” remove all jumpers
Module Address
Jumper
Select D1 Select D2
Green LED On
Point Active
I/O Point
#01
F3 F2 F1
Dual (Red/Green)
Fuse Blown LED
F6 F5 F4
F9 F8 F7 Red On = Sourcing
Current
Green On = Sinking
Current
Individual Fuses F12 F11 F10
for Each I/O Point
#12
Digital I/O Point

LED Indicators
Figure 1. Digital I/O Module Model # 68-6011 - Jumper Settings
2 TB-980802 ALL.71+
TB-980802 Digital I/O Modules: Installation Options
Getting Tech Support Digital I/O Module Model # 68-6211

Technical support is Digital Module # 68-6211 has the same features as the Model # 68-6011, plus
available at: the following:
(281) 240-6161
❑ Surface-mounted circuitry
the WEB Page at: ❑ Individual resetable fuses for each digital I/O point
www.omniflow.com
or email to:
❑ Redesigned user-selectable jumpers for IRQ polarity, channel assign,
and module address selection using 1 or 2 digital I/ O modules.
User-selectable jumper settings are shown in Figure 2 (below). When using a
second digital I/O (D2) module, no jumper is required on JP1 and JP2.
Interrupt Request (IRQ) Neither Jumper is Required for D2 Module

Select Jumpers for
Pipe Prover Detector Assign IRQ to Assign IRQ to
(Non-Double Chronometry) I/O Point #1 I/O Point #2
JP2 JP2
JP1 In = Rising Edge Trigger
JP1 Out = Falling Edge Trigger
JP1 JP2
JP4
JP5
Green LED On
Point Active
Module Address
Jumper I/O Point
I/O Point
#01 #01
F3 F2 F1
Dual (Red/Green)
ADDRESS JP4 JP5 Fuse Blown LED
D1 Out Out F6 F5 F4
D2 In Out
Red On = Sourcing
F9 F8 F7 Current
Green On = Sinking
Current
Individual Resetable F12 F11 F10
Fuses for Each I/O Point
#12
#12
Digital I/O Point

LED Indicators
Figure 2. Digital I/O Module Model # 68-6211 - Jumper Settings
TB-980802 All.71+ 3
This Page Has Been Left Blank Intentionally
4 TB-980802 ALL.71+
Date: 09 05 05 Author(s): I. P. TB # 980803B
Upgrading Flow Computer Firmware
Contents
User Manual Reference - Scope................................................................................................................... 1
information contained in Safety Considerations ....................................................................................... 2
Volume 1, applicable to all
firmware revisions. This Instructions (OmniCom for DOS Users) .......................................................... 3
technical bulletin replaces
and invalidates TB-980301 Installing New OmniCom PC Configuration Software ................................................. 3
“Upgrading EPROM
Chips”. Instructions (OmniCom for Windows Users) .................................................. 5
Installing New OmniCom for Windows PC Configuration Software ............................ 5
Replacing the Central Processor Module (CPU) and EPROM Chips ............................ 7
▲ IMPORTANT! ▲
Resetting RAM .............................................................................................................. 8
After Replacing CPU Verifying and Updating Information of Installed Modules (Check I/O Modules) ............. 9
Setting the Number of Digits and Decimal Places for Totalizers.................................. 10
Before Transmitting
Special Instructions If Upgrading from Revision 20.56 Firmware ............................................. 11
must perform the ‘Check Transmitting the Configuration File from OmniCom to the Flow Computer............... 12
(see page 9 in this bulletin)
Returning the Old EPROMs ........................................................................................ 13
and calibrate your analog Troubleshooting Tips....................................................................................... 14
I/Os before transmitting the
configuration file to the Keypad is Locked ........................................................................................................ 14
upgraded flow computer. Omni Display Does Not Come On After Resetting
Also, you must reset RAM All RAM or Omni Front Panel Display is Blinking........................................................ 14
technical bulletin before Message “Cannot Open File” is Displayed when
transmitting the Trying to Transmit the Saved Report Templates to the Omni...................................... 15
configuration file. These Incorrect Data In Printed Customized Reports ............................................................ 15
procedures must be
performed whether or not a Unable to Complete a Prove Sequence....................................................................... 15
corresponding message is OmniCom Unable to Communicate with the Flow Computer....................................... 16
computer. Failure to do so
Scope
your flow computer. This technical bulletin is applicable to all firmware revisions of Omni 6000/Omni 3000
Flow Computers. The information contained in this technical bulletin is targeted to
qualified professionals only.

Abstract
DANGER! Upgrading Omni flow computer firmware allows users to incorporate new features and
increase the capabilities of their flow metering system application. An upgrade may
also be necessary for system conformance to API standards and Year 2000 (Y2K)
requirements.
To upgrade your flow computer firmware you will need to perform certain critical steps,
such as:
Electrical Shock Hazard!
Dangerous AC voltages are Install new version of OmniCom Configuration PC Software.
present on the power supply
module and ribbon cable Save flow computer configuration file and custom report templates.
when the unit is AC
powered. To avoid electrical Replace Central Processor Module or EPROM chips.
shock which could be fatal,
It is imperative that you
Reset RAM.
remove all power before Set the number of digits and decimal places for totalizers and correction factors.
opening and disassembling
the flow computer and take Download and adjust flow computer configuration file and report templates.
any other necessary
precautions.
Only qualified technicians
should work on any internal Safety Considerations
circuitry. Omni Flow
Computers, Inc. is not Before removing any circuit boards from the flow computer, the following must be
responsible for personal observed:
injuries or accidents that
may occur when working on
flow computer circuitry. Personal Safety : Although most of the internal circuits are powered by
relatively low voltages, dangerous AC voltages are present
on the power supply module and ribbon cable when the unit
▲ CAUTION! ▲ is AC powered. For this reason it is important to remove all
Static electricity can power before disassembling the flow computer.
damage flow computer
circuitry. Take approved Static Electricity: Static electricity can be generated simply by moving around
static device handling on certain surfaces or wearing certain types of clothing. The
precautions when working
on the flow computer. flow computer’s printed circuits can be damaged by this
static electricity. Take approved static device handling
precautions when working on the flow computer.
available at:
(281) 240-6161
the WEB Page at:
www.omniflow.com
or email to:

Instructions (OmniCom for DOS Users)

If upgrading to xx.73 or older EPROMs, before removing the Central Processor Module
(CPU) or old EPROMs, you must install the new version of OmniCom for DOS
Configuration PC Software supplied with your new CPU or EPROMs and use this new
version to retrieve the configuration file from the flow computer.
Installing New OmniCom PC Configuration Software

Context sensitive help is (1) With the old EPROMs still in the flow computer, install the new OmniCom for
available by pressing the DOS software on your PC from the diskette/CD shipped with the CPU or
[F1] key on your PC EPROMs. The diskette/CD label provides installation instructions. Do not install
OmniCom.
to the same directory as a previously installed version of OmniCom for DOS.
(2) Start the old version of OmniCom for DOS and retrieve the configuration and
custom report templates from the flow computer.

(3) Receive the configuration file from the OLD set of EPROMs installed in the
flow computer by using ‘Online/Start Comm’ and selecting ‘Receive Omni
Configuration Data’.
(4) Subsequently, receive ALL the custom report templates by selecting ‘Receive
Report Templates’ within the ‘Online/Start Comm’ menu. As a precautionary
measure, this should be done regardless of whether or not custom report
templates are being used in the Omni.
(5) Print the configuration file from OmniCom to your PC or network printer by
using ‘File/Print’ and selecting your print option of LPT1 or LPT2. You must
have your MS Windows virtual printer captured to an LPT port to print from
OmniCom for DOS. See your IT department for assistance.
(6) Close the old OmniCom and start the new OmniCom for DOS. Create a new
file in OmniCom by selecting ‘File/New’ and entering the file name.
(7) When prompted for the EPROM version number of the new file to create,
select the version number that corresponds to the NEW EPROMs you will be
installing, not the version of the EPROMs currently installed.
(8) Execute steps 3 and 4 again as shown above.
(9) Verify all settings indicated in your new configuration file with the configuration
file printout from step 5 above and make any necessary adjustments to these
settings that are appropriate for your particular application.
(10) Close OmniCom by selecting ‘Exit’ from the ‘File’ menu. You will be prompted
on whether to save the configuration file and each of the report templates.
Answer ‘Yes’ to all.
(11) Go to the section in this technical bulletin entitled “Replace the Central
Processor module (CPU) and EPROM Chips”.

Instructions (OmniCom for Windows Users)

Before removing the Central Processor Module (CPU) or old EPROMs, see steps 1
and 2 below to make a determination on exactly how to proceed.
Installing New OmniCom for Windows PC Configuration

Software
Context sensitive help is (1) If you are upgrading from xx.73 (or older EPROMs) to xx.74+ EPROMs, with the
available by pressing the old EPROMs still in the flow computer, use the old OmniCom for DOS software on
[F1] key on your PC your PC to retrieve the OmniCom configuration and custom report templates from
OmniCom. the flow computer. Skip to step 5 below for instructions on how to do this,
otherwise go to step 2 below if you are upgrading from xx.74+ EPROMs to a
newer release of xx.74+ EPROMs.

(2) If you are replacing xx.74+ EPROMs with newer xx.74+ EPROMs, using the
version of OmniCom for Windows currently installed on your PC, retrieve the
configuration from the Omni and save it to your PC.
(3) Use the Add/Remove Programs feature in MS Windows Control Panel to remove
the current version of OmniCom for Windows if it is older than the version you
received with your CPU or EPROM shipment.
(4) Install the new OmniCom for Windows from the CD or from whatever directory you
saved the install executable file to if you received the new version of OmniCom for
Windows by other than CD media. You should now skip to the section labeled
“Replacing the Central Processor Module (CPU) and EPROM Chips”.
(5) Receive the configuration file from the OLD set of EPROMs installed in the flow
computer by using ‘Online/Start Comm’ and select ‘Receive Omni
Configuration Data’. Note: You must first create or open an existing file in
OmniCom for DOS before you can attempt to go online to receive the
configuration from the flow computer. If you create a new file using the
File/Create feature, you will be prompted for a filename and a revision of file to
create. Choose the revision of file that matches the version of EPROMs currently
installed in the flow computer.
(6) Subsequently, receive ALL the custom report templates by selecting ‘Receive
Report Templates’ within the ‘Online/Start Comm’ menu. As a precautionary
measure, this should be done regardless of whether or not custom report
templates are being used in the Omni.
(7) Close the OmniCom for DOS program by selecting ‘Exit’ from the ‘File’
menu. You will be prompted on whether to save the configuration file and each
of the report templates. Answer ‘Yes’ to all.
(8) Install and then start the OmniCom for Windows program. Using the File/Import
feature, import the OmniCom for DOS configuration file you saved in the previous
step above. Note: The file will have a .OMI extension and will be located in the
appropriate application subdirectory under the OmniCom for DOS install directory.
Example file to import: C:\OMNICOM\OMNI20\ABC.OMI
(9) Select the Reports icon at the top menu bar in OmniCom for Windows. Highlight
each of the report templates individually on the left side menu tree and use the
File/Import feature to individually import the OmniCom for DOS custom report
templates. The four OmniCom for DOS report templates will be in the same
directory as the configuration file you retrieved in step 8 above but will have the
following extensions.
Snapshot Report Template = .TP1
Batch End Report Template = .TP2
Daily Report Template = .TP3
Prove Report Template = .TP4
(10) Using the File/Save feature, save the configuration file and custom report
templates to the directory where you currently have OmniCom for Windows
installed in. Example: C:\OMNIFLOW\OMNICOM\ABC.o20.

Replacing the Central Processor Module (CPU) and EPROM

Chips
▲ CAUTION! ▲
(1) If you are replacing ONLY the EPROM chips and NOT the CPU module, reset
When removing the CPU all RAM in the Omni via the front panel keypad. If you will be replacing the
Module, take extreme care entire CPU module, DO NOT reset the RAM.
not to bend or fold the
membrane keypad ribbon To reset RAM from the front panel keypad, press [Prog] [Setup] [Enter]
cable too sharply, or the [Enter] [Enter], then type in your privileged password as prompted. Scroll
metallic traces could be
damaged. down by pressing the [ ] key to the ‘Reset All Ram?’ prompt and answer [Y]
to answer ‘yes’. Answer ‘Yes’ or ‘OK’ to any warnings. (Go to Step 14 for
Location of EPROM detailed instruction on resetting Ram.)
Chips- The location of the
EPROM chips on the CPU
Module is shown in Fig. 1. (10) Remove power from the Omni flow computer and remove the CPU module.
The EPROMs are the two
large 32-pin Integrated
Circuits (ICs or “chips”) with (11) Make note of the new EPROM version and checksum indicated on the label
labels marked U3 and U4. placed on the EPROM chips. You will need this information later.
Note the position of the
orientation notches at one
end of each EPROM. (12) Either replace the old CPU module with a new CPU that has the new set of
EPROMs, or simply replace the old set of EPROMs with the new set.
▲ IMPORTANT! ▲
(13) After replacing or reinstalling the CPU module, apply power to the Omni flow
Replacing EPROM Chips -
Ensure that all pins plug into
computer. Make a note of what your LCD screen displays when powering up.
there respective holes and If you receive a display indicating loss of calibration data, you will need to
that none are bent. calibrate your analog I/Os after you have completed the EPROM upgrade and
transmitted the configuration file. (Refer to Volume 1 “System Architecture
▲ IMPORTANT! ▲ and Installation” of the User Manual for more information.) If the flow
computer does not power up to the Status screen, go to the Troubleshooting
After Replacing CPU Tips section of this Technical Bulletin.
Before Transmitting the
may be required to perform
the ‘Check I/O Modules’
Math
procedure (see related Central Program Program Archive
Processor
section in this bulletin) Processor EPROM RAM RAM
before transmitting the
upgraded flow computer
and calibrating the analog
I/Os. Also, you must reset
RAM as expressed in this
transmitting the Backup
configuration file. These Batttery
procedures must be
LCD screen of the flow EPROM Size
computer. Failure to do so 1 OR 4 Meg Bit System Watchdog
may void the warranty and Select 4 Meg J3 In = Enabled
cause future problems and As Shown J3 Out = Disabled
unpredictable results with J1 J2 (Always Enabled)
your flow computer. J3
Figure 1. Layout of Central Processor Module Showing Location of

EPROM ICs and Jumpers J1, J2 and J3.

Resetting RAM
▲ IMPORTANT! ▲ (14) You will need to reset RAM before and after replacing EPROM chips. If you will
After Replacing CPU be replacing the entire CPU module, reset RAM only AFTER replacing the
Module or EPROMs and CPU. DO NOT reset the RAM before replacing. When power is applied to the
Before Transmitting the flow computer after replacing EPROM chips, the following screen is displayed.
may be required to perform If the screen does not appear as below, go to the Troubleshooting Tips section
the ‘Check I/O Modules’ of this Technical Bulletin.
procedure (see related
section in this bulletin)
before transmitting the RAM Data Invalid
configuration file to the Reconfigure System
Using “OMNI” as
I/Os. Also, you must reset Initial Password
technical bulletin before Enter the key press sequence [Prog] [Setup] [Enter] [Enter] [Enter] and the
transmitting the following screen is displayed:
procedures must be
performed whether or not a PASSWORD MAINTENANCE
displayed on the front panel Privileged _
LCD screen of the flow Level 1
computer. Failure to do so Level 1A
unpredictable results with Different screens will be displayed each time you press enter before you reach
your flow computer. the above screen.
Program Mode - Pressing (15) At the ‘Privileged’ prompt, enter the following key press sequence to use
the [Prog] key will activate ‘OMNI’ as the privileged password: [Alpha Shift] [Alpha Shift] [O] [M] [N] [I]
the Program Mode. While in [Enter]. The cursor will move down to the next entry.
To exit the Program Mode, PASSWORD MAINTENANCE
repeatedly until the Program
Privileged OMNI
LED goes off. Level 1 _
Level 1A
(16) Scroll down by pressing repeatedly the [ ] key to ‘Reset All Ram?’ and press
[Alpha Shift] [Y] [Enter] for ‘Yes’.
Archive Run?(Y/N)
Reset All Totals
Reset All Ram ? Y
The display will briefly go blank, the backlight will go off and come back on.
The following screen may then reappear:
RAM Data Invalid

Reconfigure System
Using “OMNI” as
Initial Password

(17) Press [Status] and a screen similar to the following will be displayed:
Module S-Ware H-Ware

B-1 Y Y
E-1 Y Y
D-1 Y Y
(18) Scroll down by pressing repeatedly the [ ] key to the end to display the
Revision Number and EPROM Checksum.

S-1 Y Y
Revision No. 021.72
EPROM Checksum 2408
Verify that these match with what you previously noted in Step 11. If they do
not match and there is an EPROM Checksum alarm, stop at this point and
contact Omni technical support.
▲ IMPORTANT! ▲
Verifying and Updating Information of Installed Modules
After Replacing CPU
Module or EPROMs and (Check I/O Modules)
Before Transmitting the
Configuration File - You (19) If the EPROM Revision number and Checksum are correct, verify if both the
may be required to perform
‘S-Ware’ (Software) and ‘H-Ware’ (Hardware) columns read ‘Y’ (Yes) for all the
the ‘Check I/O Modules’
procedure (see related installed modules before proceeding any further. Scroll up and down the
section in this bulletin) screen in the previous step by using the [ ] / [ ] arrow keys to view installed
before transmitting the modules. If both columns read ‘Y’, go to Step 25. If not, proceed to the
following step (20).
I/Os. Also, you must reset Module S-Ware H-Ware
B-1 Y Y
transmitting the E-1 Y Y
configuration file. These D-1 Y N
procedures must be S-1 N Y
corresponding message is Revision No. 021.72
displayed on the front panel EPROM Checksum 2408
computer. Failure to do so
may void the warranty and (20) If one or more of the installed modules reads ‘N’ (No) under the ‘S-Ware’
unpredictable results with (Software) and/or ‘H-Ware’ (Hardware) columns, press [Prog] [Setup] [Enter]
your flow computer. [Enter] and the following is displayed:
Program Mode - Pressing

the [Prog] key will activate *** MISC. SETUP ***
the Program Mode. While in Password Maint?(Y) _
this mode, the Program LED Check Modules ?(Y)
To exit the Program Mode, Config Station?(Y)
repeatedly until the Program Different screens will be displayed each time you press enter before you reach
LED goes off. the above screen.

(21) Move the cursor down by pressing the [ ] key to ‘Check Modules?’.
*** MISC. SETUP ***

Password Maint?(Y)
Check Modules ?(Y) _
Config Station?(Y)
(22) Press [Enter] and a screen similar to the following is displayed:

B-1 Y Y
E-1 Y Y
D-1 Y N
(23) Scroll down by pressing repeatedly the [ ] key to ‘Update S-Ware?’ and
press [Alpha Shift] [Y] [Enter] to enter ‘Y’ for ‘Yes’.

D-1 Y N
S-1 N Y
Update S_Ware ? Y
You will be prompted to enter your password. Also enter ‘Y’ to answer ‘OK’ if
cautioned that updating the software will cause the I/O configurations to be
cleared.
repeatedly until the Program LED above the keypad goes out. This returns you
to the Display Mode.
Setting the Number of Digits and Decimal Places for Totalizers
(25) In some newer versions of EPROMs, you are given an option to set the
number of digits for cumulative totalizer rollover (8 or 9 digits) and the number
of decimal places for volume and mass totalizers. Set these options via
keypad ONLY by pressing [Prog] [Setup] [Enter] [Enter] [Enter]. The
following screen is displayed:
Privileged _
Level 1
Level 1A
Different screens will be displayed each time you press enter before you reach
the above screen.

(26) At the ‘Privileged’ prompt, enter the following key press sequence to use
‘OMNI’ as the privileged password: [Alpha Shift] [Alpha Shift] [O] [M] [N] [I]
[Enter]. The cursor will move down to the next entry.
Setting the Number of
Digits for Totalizers - PASSWORD MAINTENANCE
Totalizers within the flow Privileged OMNI
computer can be rolled at 8
or 9 significant digits. To set Level 1 _
totalizer rollover to 9 digits, Level 1A
press [0] [Enter]. To set
totalizer rollover to 8 digits,
press [1] [Enter].
(27) Scroll down by pressing repeatedly the [ ] key to ‘Reset All Totals?’.
Setting Volume and Mass
Totalizer Resolution - PASSWORD MAINTENANCE
Gross and net volume and Reconfig Archive ? Y
mass totalizer values can
be expressed with up to 3
Archive Run?(Y/N) N
decimal places. To set the Reset All Totals ? _
number of decimal places
for totalizer resolution, press
the corresponding number
key ([0], [1], [2] or [3] (28) Press [Alpha Shift] [Y] [Enter] for ‘Yes’ and a screen similar to the following is
decimal places, where displayed:
0=Klbs, 1=100lbs, 2=10lbs,
3=lbs). Then press the
[Enter] key. All firmware All Totals Now Reset
revisions, except for Version Totalizer Resolution
20.56, provide Mass in
pounds. # Digits, 0=9, 1=8 0
DecPlacesGross&Net 0
DecimalPlaces Mass 3
Help for Number of Digits
and Decimal Place
Settings - You can view the Enter the respective values you want for each and every totalizer resolution
Help in OmniCom under
setting and press the [Enter] key after each entry (see sidebar).
“Factor Setup & Sys
Constants” by highlighting It is strongly recommended that you set these resolutions NOW because you
each of the fields. Then use
F1 for a detailed explanation will not be able to change these settings after configuring your flow computer
of each of your choices. or during flow operations without resetting to zero all your totalizers.
However, DO NOT set
these options via OmniCom.
Context-sensitive help is Special Instructions If Upgrading from Revision 20.56 Firmware
also available via the Omni
front panel keypad by Version 20.56 EPROMs provide Mass in hundreds of pounds. If you want to
pressing the [Help] key continue receiving your Mass in hundreds of pounds, press [1] [Enter] at the
(same as the [Enter] key) ‘DecimalPlaces Mass’ entry.
twice within one second
while the cursor is at the
entry you want to set. Press (29) Exit the Program Mode when you are done by pressing the [Prog] key
[PROG] key once to exit repeatedly until the Program LED above the keypad goes out. This returns you
Help.
to the Display Mode.

Transmitting the Configuration File from OmniCom to the

Flow Computer
Program Mode - Pressing (30) In the Display Mode, press [Prog] [Setup] [Enter] [Enter] to display the ‘Misc.
the [Prog] key will activate
the Program Mode. While in Setup’ menu.
above the keypad is lit red. *** MISC. SETUP ***
press the [Prog] key Password Maint?(Y) _
repeatedly until the Program Check Modules ?(Y)
LED goes off. Config Station?(Y)
Different screens will be displayed each time you press enter before you reach
the above screen.
(31) Scroll down by pressing repeatedly the [ ] key to ‘Serial I/O “n”’.
*** MISC. SETUP ***

User Display ? “n”
Config Digital“n”
Serial I/O “n” _
Enter the number of the flow computer serial port to which your OmniCom PC
is connected and press [Enter]. A screen similar to the following will display:
SERIAL PORT #2
Baud Rate 38400
Number of Data Bit 8
Number of Stop Bit 1
▲ IMPORTANT! ▲ (32) Scroll down to ‘Modbus ID’ and then to ‘Modbus Type’ and enter the
corresponding settings indicated in the OmniCom configuration file you saved
It is recommended that you
select ‘Modbus RTU
and printed earlier. Remember to press [Enter] after typing each setting.
(modem)’ protocol for the
‘Modbus Type’ in Step 32 if SERIAL PORT #2
it is available in your new
EPROM version. If you
TX Key Delay 1
decide to use this protocol, Modbus ID 1
ensure that you make this Modbus Type 2
same change in your
OmniCom configuration file
under ‘Config Serial I/O’
(33) Print the configuration file from OmniCom for DOS to your PC or network
before proceeding to
download the configuration printer by using ‘File/Print’ and selecting your print option of LPT1 or LPT2.
file to the Omni Note: You must have the MS Windows virtual printer captured to an LPT port
to print from OmniCom for DOS. See your IT department for assistance.
In OmniCom for Windows, use the Configure/Configuration Print/Print

Report feature.
(34) Open ‘Offline/Omni Configuration/Config Serial I/O’ and ensure that the
‘Modbus Type’ is set correctly to match what you selected in Step 32.

(35) In OmniCom for DOS, go to ‘Online/Start Comm’. Check the Modbus ID,
Comm Port, Baud Rate, and Comm Media settings to ensure that these are
correct. If you set the port in Step 32 to ‘Modbus RTU (modem)’ protocol,
ensure that ‘Comm Media’ is set to Modem in OmniCom for DOS. Note: If
using OmniCom for Windows, you would set the media type in the
Edit/Sites/Media Type setting when configuring a site to connect to. You
would then press on the globe icon on the menu bar at the top of your screen
and select the site and flow computer you would like to connect to.
(36) Transmit Omni Configuration Data and then the Custom Report Templates.
Note: If using OmniCom for Windows, the custom report templates are
automatically transmitted for you when transmitting the configuration file,
assuming they exist on your PC and the names are associated with the
transmitted configuration file.
(37) While in the online mode, check all of your configuration settings to ensure
they are correct.
(38) Calibrate your analog I/Os if you are required to do so. For more information on
calibrating analog I/O, see Volume 1, Chapter 8 of the User Manual.
Returning the Old EPROMs

Remember to use the Business Reply Label supplied with your new EPROMs. If you
have not yet completed your EPROM Upgrade Form, please do so now and return
along with the old EPROMs to Omni Flow Computers, Inc.

Troubleshooting Tips
Keypad is Locked
Proceed as follows if keypad is locked (i.e., Program Lockout message is displayed
when attempting to make changes via the keypad):
(1) Pull out the chassis and locate the Program Enable/Lock switch located
behind and towards the bottom of the keypad assembly. Move the switch to
the Enable position.
▲ CAUTION! ▲ Proceed as follows if keypad is locked (i.e., not functioning):

CAUTION: PRESSING THE RESET SWITCH WILL CAUSE YOU TO LOSE
It is recommended that you
stop flow before pressing
the Reset Switch on the flow APPROXIMATELY 1.5 SECONDS OF FLOW. THEREFORE, IT IS
computer as it will cause RECOMMENDED THAT YOU STOP FLOW BEFORE PRESSING THE RESET
you to lose approximately
1.5 seconds of accumulated
SWITCH.
flow. Pressing and (1) Press the spring-loaded Reset switch located behind the LCD screen and
releasing this switch has the
same effect as
towards the top of the keypad assembly.
disconnecting power to the
flow computer and then
reapplying power. Omni Display Does Not Come On After Resetting All RAM or
Omni Front Panel Display is Blinking
Proceed as follows if display is blinking or two rows of squares are displayed:
(2) Remove CPU Module, located directly behind the keypad assembly, and
remove the System Watchdog Jumper J3, located on the module, near the
battery.
(3) Reinstall CPU Module with Jumper J3 removed.
(4) Power up the Omni. The display may show two rows of squares or may be
blinking.
(5) Power down again and remove the CPU module.
(6) Replace Jumper J3 and then reinstall the CPU Module.
(7) Once again, apply power to the flow computer.
The Omni display should now power up into the Status screen showing the status of
each of the hardware modules. If problem persists, reset the ram on the CPU
module as follows:

(3) Remove the four RAM chips in slots U5 through U8 on the CPU board.
▲ IMPORTANT! ▲ Reinsert them, inserting U5 last, taking care not to bend any pins on the ram
chips. If you have a newer style CPU board with a ram daughterboard, short
Replacing RAM and
EPROM Chips - Ensure
the two pins labeled CLR with a paper clip in order to reset ram. Do not use a
that all pins plug into their screwdriver as some screwdrivers are coated with a non-conductive material.
respective holes and that
none are bent.
(5) Apply power and the display should now come up to the normal Status screen.
Message “Cannot Open File” is Displayed when Trying to

Transmit the Saved Report Templates to the Omni
Go to the OmniCom for DOS pull-down Report menu and open each of the reports
templates individually, make the necessary changes and resave the reports. If you
see a blank page, this means you are not using custom report templates. The
change can simply represent change to the same thing it was before. Save the
template using ALT-S, exit OmniCom, and restart OmniCom. Open the file and
transmit the custom report templates.
Incorrect Data In Printed Customized Reports

When upgrading EPROMs and using customized reports, the data in the printed
report may not be correct because some of the database registers may have
changed, moved or been redefined in the new version with respect to the old
version. If you see that printed data is not what was expected, then you should open
the report template files to check if the data is being retrieved from the correct
registers for the new EPROM version. Also verify in OmniCom that “Use Default
Report Templates’ under ‘Printer Setup’ is set to ‘No’ when using custom report
templates.
Note: When using xx.74+ firmware, In the Configure/Reports menu of OmniCom for
Windows, instead of having a global setting for all four reports (i.e., SnapShot,
Batch End, Daily, and Prove) you are now allowed to have a mix of customized and
default report templates. Ensure that you check or uncheck the appropriate box for
each report template based on your preference.
Unable to Complete a Prove Sequence

Sometimes you are unable to get through a prove sequence after an EPROM
upgrade. Open up the deviation percentages in the Prover Setup menu to establish
an initial prove sequence. Also ensure that you have selected the option NOT to
implement the prove meter factor. Once a prove sequence has completed
successfully, you can tighten up the deviation percentages to what you had set
before the EPROM upgrade. If you were previously auto-implementing a prove
meter factor, you can change the setting back in the Prover Setup menu after a
successful prove sequence.
Note: In OmniCom for Windows, these settings are found in the Configure/Prover
menus.

OmniCom Unable to Communicate with the Flow Computer
Sometimes you are unable to communicate to an Omni after replacing the EPROMs.
This may be caused by the following:
▲ IMPORTANT! ▲
The OmniCom for DOS Start Comm/Comm Media setting differs from the
Omnicom for DOS and MS Omni flow computer Modbus Type setting in the serial port setup. In the
Windows XP or MS
Windows 2000- If you are
newest versions of EPROMs when the flow computer is powered-up, the
experiencing problems EPROMs default to Modbus RTU Modem for Serial Port # 2. The Modbus RTU
communicating with the flow Modem protocol is the preferred protocol instead of the Modbus RTU protocol;
computer, ensure that your therefore, make this change in your OmniCom configuration file AND also set
MS Windows processor
scheduling setting is
the ‘Comm Media’ to ‘Modem’ in the ‘Online/Start Comm’ menu. Note: If
configured for Background using OmniCom for Windows, ensure that when you configured a site in the
Services to allow equal Edit/Sites menu, that you specified Direct for the Media Type setting if you
amounts of processor time have a direct serial connection to the Omni. In OmniCom for Windows, only if
to all resources.
you have an actual modem should you set the type of connection as Modem.
The new EPROMs default to Modbus ID 1 on power-up. Ensure that your
Modbus ID matches in both the ‘Online/Start Comm’ menu and in the serial
port setup in the Omni. Also ensure the OmniCom configuration file, Omni
serial port, and OmniCom ‘Start Comm’ screen are all set to the same Modbus
ID. Note: In OmniCom for Windows, this setting is found in the
Configure/Ports menu.

Date: 05 29 2003 Author(s): R. S. TB # 981101
Using the Audit Trail (Event Logger) Feature

and Sealing of the Flow Computer
Contents
complements the
information contained in Activating the Audit Trail Feature ..................................................................... 2
Volumes 2 & 3 of the User Password Protecting Serial Port Access ....................................................................... 3
Manual, applicable to all
firmware revisions. Enabling Rigorous Auditing of Serial Ports.................................................................... 4
Printing and Viewing the Audit Trail Report .................................................... 5
Printing the Audit Trail Report via Front Panel Keypad ................................................. 5
Viewing and Printing the Audit Trail Report via OmniCom ............................................ 5
Audit Trail Feature Sealing the Flow Computer ............................................................................... 6
This feature is an event Download Disabling (OmniCom Lockout)...................................................................... 6
logger that records the last
Serial Port Lockout Switch Enable Option ..................................................................... 7
150 changes made to the
flow computer database. A Program Inhibit (Keypad Lockout) Switch...................................................................... 7
fixed format report provides Housing Sealing ............................................................................................................ 8
an audit trail of these
changes. This report
comprises time and date
stamped changes made to
the flow computer database,
either via the local keypad
or via password protected
serial port access. Scope
All firmware revisions of Omni 6000/Omni 3000 flow computers have the Audit
Trail feature. The information contained in this technical bulletin is for
intermediate users.

Abstract
All Omni flow computer firmware revisions include the “Audit Trail” feature. In
current revisions, this security feature consists of an archive file that stores 150
records of the most recent changes made to the flow computer database. The
flow computer always logs changes made to the database via the Omni front
panel keypad. It can also log changes made remotely via a Modbus port, using
OmniCom PC Configuration Software for instance, if passwords have been
Getting Technical Support
activated on the serial port.
available at:
Each record consists of a unique event number, time and date tag, the database
(281) 240-6161
index number of the affected variable, and the new and old value of that
variable. The value of gross and net totals at the moment of the event are also
the WEB Page at: stored in the record. Furthermore, the firmware can log events that involve a
www.omniflow.com group of consecutive database addresses. In this case, only the starting index
or email to: number and the number of consecutive index points appear in the audit trail.
The records comprise the Audit Trail Report which, when printed, lists the latest
150 records in time sequence starting with the most recent. You can view this
report in OmniCom and print it either with OmniCom or the front panel keypad.
The Audit Trail Report has a fixed format and is not customizable by the user.
Activating the Audit Trail Feature

The Omni flow computer will automatically log all changes made to the
configuration settings via the front panel keypad. However, to avoid flushing the
audit trail, the firmware does not log configuration changes made via serial ports
other then complete download events, unless rigorous auditing is enabled. In
order for the flow computer to log configuration changes made through a serial
port, whether remotely (via modem) or via direct connection, the corresponding
serial port must be password protected or enabled for rigorous auditing.
With passwords activated, the firmware will fully log the target database
address’ old and new value only when single point writes occur. When blocks of
data are written, only the starting database index and total number of
consecutive points written to will be recorded in the audit trail log.
Enabling rigorous auditing does not require serial port passwords to be used.
The flow computer will archive all serial port transactions that represent
configuration changes.

TB-981101 Using the Audit Trail Feature (Event Logger) and Sealing the Flow Computer
Password Protecting Serial Port Access

Entering a Serial Port
Password The flow computer will automatically log any single point writes to a specific
Initially, you can only assign database address made via a password protected serial port. Assigning serial
serial port passwords via port passwords for the first time can only be done via the front panel keypad of
the Omni front panel the flow computer.
keypad. Choose up to 8
alphanumerical characters
for the password. Enter the To assign passwords and restrict access to serial ports via the Omni front panel
selected password at the keypad, proceed as follows:
corresponding serial port
entry under the ‘Password
Maintenance’ submenu:
(1) Using the flow computer’s front panel keypad and in the normal display
❑ ‘Ser1 Passwd’ for Serial
Port #1 mode, press [Prog] [Setup] [Enter] [Enter] [Enter]. This will display the
❑ ‘Ser2 Passwd’ for Serial ‘Password Maintenance’ submenu of the ‘Miscellaneous
Port #2 Configuration’ menu.
❑ ‘Ser3 Passwd’ for Serial
Port #3 PASSWORD MAINTENANCE
❑ ‘Ser4 Passwd’ for Serial Priveledged _
Port #4 Level 1
Note: If Serial Port #1 has a Level 1A
printer connected to it, you
need not assign a password
to this port. Ports #3 and #4
are available only if your
flow computer has a second (2) Scroll down to place the cursor at the desired ‘Sern Passwd’ prompt and
serial I/O module installed. enter a password of your choice. The “n” in ‘Sern’ represents the serial
port number (e.g., the display shows Ser2 for Serial Port #2 see
sidebar).
Ser1 Passwd
Lockout SW Active? N
Ser2 Passwd _
(3) Press [Enter] once you have keyed-in your password for the selected
serial port. The flow computer will prompt you to enter the privileged
password for the flow computer to validate the new serial port password.
If you have not yet assigned a privileged password, either use “OMNI” as
the default or scroll up and assign the password now. If you do the latter,
repeat the procedure for assigning the serial port password.
Once assigned, you have the option of changing the serial port passwords via
OmniCom PC configuration software. To do this, while on any field edit screen,
press [Ctrl] [Alt] [P] on your PC keyboard and follow the online instructions.
You will need to enter the current valid password before you can change it.

Enabling Rigorous Auditing of Serial Ports

Rigorous auditing is normally used only as a diagnostic tool to track down
unexpected changes made to the flow computer database. It allows you to log
all transactions of one or more non-password protected serial ports. Actually,
the only way to log all changes to the Omni database done through serial ports
is by enabling rigorous auditing.
To enable rigorous auditing you must define a user-programmable variable

statement. This statement places the decimal value of the serial port’s
hexadecimal code into the database address the corresponds to the special
diagnostic function (Index # 3800).
To enable rigorous auditing to one or more serial ports, do the following:
(1) From the table below, select the hexadecimal codes of the serial ports to
which you want to apply rigorous auditing. Then determine the decimal
equivalent of the selected hexadecimal codes (indicated in the table).
(2) Formulate a variable statement that writes the desired decimal value to
Database Point # 3800 (Special Diagnostic Function) using the following
logic:
Address 3800 is EQUAL (=)to the CONSTANT (#) decimal value
Or simply select the respective variable statement from among those

provided in the table.
V AR I AB L E S T AT E M E N T S F O R E N AB L I N G RIGOROUS AUDITING
TO S E R I AL P O R T S
Serial Port(s) # Hexadecimal Decimal Variable
1 2 3 4 Code Equivalent Statement
n 000A 10 3800=#10
o 00A0 160 3800=#160
p 0A00 2560 3800=#2560
q A000 40960 3800=#40960
n o 00AA 170 3800=#170
n p 0A0A 2570 3800=#2570
n q A00A 40970 3800=#40970
o p 0AA0 2720 3800=#2720
o q A0A0 41120 3800=#41120
p q AA00 43520 3800=#43520
n o p 0AAA 2730 3800=#2730
n o q A0AA 41130 3800=#41130
n p q AA0A 43530 3800=#43530
o p q AAA0 43680 3800=#43680
n o p q AAAA 43690 3800=#43690

(3) Either via OmniCom or the front panel keypad, open the ‘Program
Variable’ submenu under the ‘Miscellaneous Configuration’ menu,
select an available (empty) variable point, and key-in the variable
statement. Press [Enter] when done to enable the rigorous auditing
feature. In OmniCom, remember to download the variable statement to
the flow computer when done if working offline.
Verifying the Audit Trail

Feature Printing and Viewing the Audit Trail Report
To verify that the audit trail
feature and rigorous You can print the Audit Trail Report from either the flow computer’s front panel
auditing are active, make
any necessary flow
keypad or from OmniCom. However, you can view this report only from
computer configuration OmniCom.
changes and view or print
the Audit Trail Report (as
indicated in this technical
bulletin). If the changes you
made appear on the report, Printing the Audit Trail Report via Front Panel Keypad
the audit trail feature is
working fine. To print the Audit Trail Report from the flow computer’s keypad, do as follows:
(1) In the display mode, press [Prog] [Print] [Enter] to display the ‘Print
Report Menu’.
(2) Scroll down to place the cursor at the ‘Audit Trail ? (Y)’ prompt and type
the number ‘150’, indicating the total number of records to print. It is not
necessary to print all 150 records, unless you want to.
(3) Press [Enter] and the report will print.
Viewing and Printing the Audit Trail Report via OmniCom

To print the Audit Trail Report from OmniCom, do the following:
(1) With OmniCom running, select ‘Audit Trail Report’ under the ‘Report’
menu and press [Enter].
(2) Select ‘Load from Omni’ in the popup box and press [Enter]. OmniCom
will prompt you for a password to continue. It will allow you to change the
password if you want (for loading the Audit Trail report via OmniCom
only). In any case you will need to enter the password you assigned for
rigorous auditing.
(3) Type the password and press [Enter]. OmniCom will proceed to load the
audit trail data and display the Audit Trail Report.
(4) If you want to print the report, press [Alt] [P] and follow the online
instructions.
(5) Exit OmniCom when done.

Sealing the Flow Computer

In addition to the audit trail, Omni flow computers provide sealing features for
added security. These security features prevent access to the circuitry and
tampering of configuration settings, protecting data and system integrity.
TIP The key sealing features are:

You can set the download
disabling and serial port ❑ Download Disabling (OmniCom Lockout)
lockout switches in one
session while in the ❑ Serial Port Lockout Switches
‘Password Maintenance’
setup. You can set these ❑ Program Inhibit (Keypad Lockout) Switch
features only via the front
panel keypad or using the ❑ Housing Sealing
Omni Panel Emulator
provided in OmniCom. The
recommended order for
applying the sealing
features is as follows: Download Disabling (OmniCom Lockout)
(1) Disable download to the
flow computer Omni flow computer firmware allows you to block all complete downloads from
(2) Select the serial port OmniCom to the flow computer. This feature protects against accidental
lockout switch option downloads that could occur due to incorrect logon. Once a flow computer is
(3) Activate the program
configured, the correct way to log on is to ‘Receive’ the configuration in
inhibit switch
(4) Seal the flow computer
OmniCom.
housing enclosure
You can set this feature only via the front panel keypad. To set the download
disabling feature, proceed as follows:
(1) In the normal display mode, press [Prog] [Setup] [Enter] [Enter]
[Enter] to access ‘Password Maintenance’ setup.
(2) At the ‘Privileged’ Password prompt, type-in the corresponding

password and press [Enter]. The download disabling setting will not
appear if you do not enter the privileged password.
(3) Scroll down to the ‘Disable Download?’ prompt. The LCD screen
displays as shown below.
Lockout SW Active? N
Model #? 0=3K,1=6K 1
Disable Download? N
(4) Press [Y] [Enter] to disable or [N] [Enter] to enable OmniCom

downloading of the configuration data to the Omni flow computer.
If desired, you can proceed to set the serial port lockout switches while in the
‘Password Maintenance’ setup. The following section describes this feature.

Serial Port Lockout Switch Enable Option

The flow computer’s configuration provides a lockout switch option for each
serial port. You can activate or deactivate the serial port lockout switch option
only via the front panel keypad, as follows:
(1) In the normal display mode, press [Prog] [Setup] [Enter] [Enter]
[Enter] to access ‘Password Maintenance’ settings.
(2) Scroll down to the ‘Lockout SW Active?’ setting that corresponds to the
selected serial port. Press [Y] [Enter] to activate or [N] [Enter] to
deactivate the lockout switch for each serial port to which you want to set
this feature.
(3) Press the [Prog] several times to exit the Program Mode and return to
the Display Mode.
Preventing Access to the

Program Inhibit Switch
Program Inhibit (Keypad Lockout) Switch
To prevent unauthorized
activating or deactivating of
the program inhibit switch,
The Program Inhibit Switch allows you to lock access to the Program and
seal the flow computer Diagnostic/Calibration Modes via the front panel keypad. This prevents
housing as indicated in this configuration settings from being changed. Attempting to enter a configuration
technical bulletin. submenu will have no effect when the switch is in the inhibit position, and
Activating the program “PROGRAM LOCKOUT” will display on the bottom line of the LCD screen.
inhibit switch with firmware
revisions prior to .72 Nonetheless, you can still enter key presses to only view data in the normal
blocked all configuration Display Mode.
changes. This was
subsequently modified to Figure 1 (on following page) shows the location of the program inhibit switch;
allow configuration changes
to password level 2 which is behind the front panel. To access and activate or deactivate, do the
operational parameters following:
such as PID setpoints,
batch end commands, and
(1) Hold the front panel from the bottom, gently lift it upwards to disengage
prove commands.
the latching bezel, and withdraw the flow computer a couple of inches
from its housing case.
(2) Locate the red Program Inhibit Switch. It will be on the bottom right
(when facing the front panel) behind the front panel (see Figure 1).
(3) Using your right hand (recommended), place the switch to the downward
position to lock the keypad or place it to the upward position to unlock
the keypad.
(4) Reinsert the flow computer into its housing, making sure that the bezel
latches in place.
You can test the program inhibit switch by pressing the [Prog] [Setup] [Enter]
keys on the front panel keypad. This will take you to the Setup Menu in the
Program Mode. Place the cursor on any of the submenus listed and press
[Enter]. If the “Program Lockout” message flashes on the bottom line of the
LCD screen, the program inhibit switch is active.

CAUTION!
These units have an
integral latching mechanism
which you must first
disengage by lifting the
bezel upwards before
withdrawing the unit from
the case.
Figure 1. The Program Inhibit Switch
Housing Sealing
You can lock or seal the inner enclosure of the flow computer within the outer
enclosure, blocking access to the 'Program Inhibit Switch' and to the circuitry. To
seal the flow computer, insert an instrument sealing wire through the holes
provided on the top-right and towards the back of the enclosures. Before placing
the sealing wire, make sure that the integral latching mechanism is in place
aligning the holes of both enclosures (inner and outer).

Last Updated: 26 Feb ‘07 Author(s): KDE/IP TB # 990101B
Communicating with Instromet® Q-Sonic®

Ultrasonic Gas Flowmeters
Contents
Scope ................................................................................................................... 1
Abstract ............................................................................................................... 1
Q-Sonic® Flowmeter Theory of Operation ...................................................... 2
complements the
User Manual, applicable to OMNI Flow Computer Logic .............................................................................. 2
Revision 23.73/27.73+.
Wiring Installation............................................................................................... 4
Communicating with Flow Computer Configuration........................................................................... 4
Instromet® Q-Sonic® Miscellaneous Configuration Meter Run Settings.......................................................... 5
Ultrasonic Gas Meter Run Setup Entries ............................................................................................... 5
Flowmeters
Flow Computer Database Addresses and Index Numbers ............................ 7
The Instromet Q-Sonic
ultrasonic flowmeter Flow Computer User Displays......................................................................... 10
measures gas flow with SV Module Serial Communications Port ..................................................................... 10
acoustic pulse reflection
paths by using the Absolute Meter Run Data ........................................................................................................... 12
Digital Time Travel (ADTT)
method. This device
communicates with Omni
flow computers via Omni’s
‘SV’ process I/O combo Scope
module using a proprietary
protocol. To use the scaled This technical bulletin applies to firmware revisions 23.73+ and 27.73+ of OMNI
pulse output of the 6000/OMNI 3000 flow computers, for gas flow metering systems.
Instromet flowmeter, the
flow computer must either
have an ‘A’, ‘B’ or ‘E’
combo module installed. Abstract
The Q-Sonic ultrasonic flowmeter determines the linear gas velocity through the
meter tube by using multiple acoustic pulse reflection paths. The Q-Sonic
analyzes these paths employing the Absolute Digital Time Travel (ADTT)
measurement method. The OMNI flow computer totalizes either the flowmeter
pulse input signal or the profile corrected gas velocity data, received from the Q-
Sonic, to calculate the actual flow rate of gas. The OMNI compensates
temperature expansion effects on the flowmeter tube by equaling the flow to the
profile corrected gas velocity multiplied by the temperature compensated tube
area. If required, it can also directly use the non-compensated flow rate value
transmitted by the ultrasonic meter as the actual flow rate.
TB-990101B 23/27.73+ 1
OMNI 6000 / OMNI 3000 Flow Computers Technical Bulletin
Q-Sonic® Flowmeter Theory of Operation

Getting Tech Support Instromet’s ultrasonic gas flow metering technology incorporates multiple pairs
Technical support is of transducers into a smart digital inferential instrumentation device. The device
available at: is installed into a gas pipeline system to measure fluid flow. Each pair of
(281) 240-6161 transducers emits ultrasonic (acoustic) pulses that travel bi-directionally, in
Email should be sent via either a single (axial or diagonal) or double (swirl) reflection path, to and from
the WEB Page at: each transducer in the pair.
www.omniflow.com
The flowmeters apply the Absolute Digital Time Travel (ADTT) method of
or email to:
ultrasonic pulse analysis, which is based on the fact that pulses travel (between
a transducer pair) faster downstream with the flow than upstream against the
flow. The gas flow velocity is determined from this upstream/downstream travel
time differential of the ultrasonic pulses within the multiple reflection paths.
When there is no gas flow in the pipeline, the upstream and downstream travel
times are the same; i.e., the time differential is zero.
The Q-Sonic flowmeter employs 3 or 5 transducer pairs with a minimum of one
axial path and two swirl paths. This configuration allows for unique combinations
of reflection paths to best take into account the different effects of gas flow
profile variations, including swirl in the pipeline. The gas velocity can be
determined for bi-directional (forward or reverse) fluid flow.
OMNI Flow Computer Logic

The OMNI flow computer can determine the actual flow rate from either data
received serially from the Q-Sonic flowmeter or from a live pulse frequency
signal input, if one has been connected and assigned.
Totalization will be based on the flow pulse frequency input when the flow
transmitted by the Q-Sonic is in the correct direction (forward/reverse) and the
pulse frequency is within limits. This live signal will also be used in the event of a
communications failure between the Q-Sonic and the OMNI. However, In order
for the OMNI to use the pulse frequency signal, it must be wired to the Q-Sonic
and an I/O point assigned in the flow computer configuration.
The flow computer will temperature compensate the meter tube area and
calculate flow rate based on the profile corrected velocity of the gas transmitted
serially by the flowmeter. If the calculated flow rate is not within reasonable
limits, the OMNI will directly use the transmitted flow rate as the actual flow rate.
2 TB-990101B 23/27.73+
TB-990101B Communicating with Instromet® Q-Sonic® Ultrasonic Flowmeters
Start
Q. Sonic
Communications
No OK?
Yes
Set Q. Sonic Clear Q. Sonic

Communication Communication
Failed Alarm Failed Alarm
No Is Transmitted
Flow Rate in
the Correct
Direction?
Yes
No No
Are Pulse I/O Are Pulse I/O Clear Pulse Signal
Assigned? Suspect Alarm
Assigned?
Yes
Yes
Is the
Flow Based No Set Pulse Signal
on Pulses Suspect Alarm
within Limits?
Yes Is the
No Flow Based on
Gas Velocity
Clear Pulse Signal within limits?
Suspect Alarm
Yes
Disable Clear Flow Set Flow Clear Flow

Totalizing Delta Alarm Delta Alarm Delta Alarm
Set Run as Calculate Actual Flow Calculate Actual Flow Calculate Actual Flow
Inactive Based on Pulse Based on Transmitted Based on Gas Velocity
Input Signal Flow Rate & Temp Comp Area
End
Figure 1. Flow computer logic flow diagram for the Q-Sonic® ultrasonic gas flowmeter.
TB-990101B 23/27.73+ 3
Wiring Installation
Serial Data Figure 2 shows the typical wiring required for connecting a Q-Sonic flowmeter
Communications to the OMNI flow computer. A 2-wire RS-485 interface can be wired to either
The serial interface between port (terminals 1 and 2 for port 1, or 3 and 4 for port 2) of the flow computer
these devices is 2-wire RS- terminal block that corresponds to the SV combo module. You can install up to
485 mode utilizing a
proprietary protocol.
two SV modules in the OMNI flow computer, which will give you an availability of
4 SV RS-485 ports. Although not required, it is recommended that the flowmeter
Setting Up and Wiring frequency pulse signals also be wired to the OMNI’s input channel #3 (forward
to Omni Combo direction) and input channel # 4 (reverse direction) of an ‘A’ combo module.
Modules Input channel #3 corresponds to terminals 5 and 6, and input channel #4 to
In order to communicate terminals 7 and 8 of the back panel terminal block respective to the combo
with Q-Sonic ultrasonic module. The actual terminal block numbers depend upon which backplane
flowmeters, the OMNI flow connector or slot the module is plugged. The ‘E’ combo module can also be
computer must be equipped used in this configuration with slight variations in wiring connections (see
with at least one SV combo
module (Model 68-6203). Volume I, Chapter 2-12).
For instructions on jumper
settings and other process
I/O combination module
setup information, please
refer to Volume 1, Chapter
2 of the OMNI User Manual
Figure 2. Example of wiring a Q-Sonic® flowmeter to the OMNI flow computer’s

RS-485 port #1 of an SV module with the recommended bi-directional
(forward/reverse) pulse output to input channels #3 and 4 of an ‘A’ combo
module.
Flow Computer Configuration

The flow configuration settings that are specific to the Q-Sonic flowmeter are
entered in the miscellaneous configuration meter run menu and the meter run
setup menu. You must enter the miscellaneous configuration meter run settings
first and then proceed to the meter run setup entries. These configuration
settings can be entered either via the OMNI flow computer’s front panel keypad
or using OmniCom configuration PC software (see Chapter 2 ‘Flow Computer
Configuration’ in Volume 3 of the OMNI User Manual, and the technical
bulletin TB-960701 ‘Overview of OmniCom Configuration PC Software’).
4 TB-990101B 23/27.73+
Miscellaneous Configuration Meter Run Settings

The following miscellaneous configuration meter run settings correspond to the
Q-Sonic ultrasonic gas flowmeter:
Select Flowmeter Device Type ⎯ Enter [4] for each meter run that you want
to select the Instromet Q-Sonic flowmeter as the device type.
Select SV Module Port ⎯ The OMNI flow computer can accept two SV
combo modules. With one SV module you have two SV ports available, and with
two SV modules four ports are available. For each ultrasonic meter run, enter the
SV port number (1 to 4) to which the RS-485 serial interface input from the Q-
Sonic flowmeter is wired to the flow computer.
Dual Pulse? (Y/N) ⎯ Enter [Y] for each meter run that will be providing dual
pulse trains for Pulse Fidelity checking. Note: This feature became available in
the flow computer for the Instromet UFM in 23.74.20 and 27.74.20 firmware.
Select Flow Direction ⎯ Q-Sonic flowmeters allow for bi-directional fluid flow
measurement. You can setup the flow computer to totalize either forward or
reverse flow on any meter run with an ultrasonic flowmeter.
Primary Flow ⎯ This setting instructs the flow computer to use either the pulse
input channel or the SV serial communications data as the primary means of
calculating flow. Options are:
0 = Select Serial Data as primary flow. This means the SV serial

communications data will be the primary and the pulse input channel, if
assigned, will be used as a backup means of flow calculations by the flow
computer.
1 = Select Pulse Input as primary flow. This means the flow pulses
received from the flowmeter will be the primary and the SV serial
communications data will be used as a backup means of flow calculations
by the flow computer.
Note: This feature became available in the flow computer for the Instromet UFM in
23.74.20 and 27.74.20 firmware.
Assign Flow Pulse Frequency I/O Point ⎯ Flowmeter pulse signals can
only be assigned to Input Channels #3 and #4 of A and E combo modules, and
input channel #3 of a B combo module. Enter the input channel number, which will
be used to input the ultrasonic flowmeter pulse signal.
Note: An E-Combo module is required for Pulse Fidelity checking. Assign the flow
rd
computer input channel number that corresponds to the 3 input channel on the E-
Combo module where the A pulse train from the flowmeter will be wired to. The
flow computer will automatically assume the B pulse train will be wired to the next
input channel.
Meter Run Setup Entries

The following meter run setup entries are available for the Q-Sonic ultrasonic
gas flowmeter:
Tube Diameter⎯ Enter the diameter of the ultrasonic flowmeter tube, in inches
(firmware 23) or millimeters (firmware 27). This diameter is subsequently
corrected for expansion due to temperature, and used together with the 'corrected
gas velocity' through the meter to calculate flow rate.
TB-990101B 23/27.73+ 5
Tube Reference Temperature⎯ Enter the temperature, as degrees

Fahrenheit (firmware 23) or degrees Celsius (firmware 27), at which the ultrasonic
meter tube was measured.
Tube Expansion Coefficient⎯ The ultrasonic meter tube will expand and
contract with temperature. The flow computer requires the linear coefficient of
thermal expansion for the meter tube material in order to correct the meter tube
area.
US Customary Units Metric Units

Mild Carbon Steel Plate -100 to 300 °F = 6.20 x e
-6
-73.3 to 148.9 °C = 1.12 x e
-5
304/316 Stainless Steel -100 to 300 °F = 9.25 x e

-6
-73.3 to 148.9 °C = 1.67 x e
-5
Q-Sonic Maximum Flow Rate Deviation Percent⎯ The actual user-

entered flow used by the flow computer to totalize depends upon several factors:
(1) If a pulse signal is available the flow computer will use it for calculations as
long as the calculated flow rate is within this 'flow rate deviation percentage'
of the flow transmitted serially by the Q-Sonic.
(2) If a pulse signal is not available or failed, the flow computer will use the
'corrected linear gas velocity' transmitted by the Q-Sonic and calculate flow
based on the 'temperature compensated area' of the meter tube. The flow
rate calculated by this method must also be within this 'flow rate deviation
percentage' of the flow transmitted serially by the Q-Sonic.
Summarizing, the flow computer first tries to use the pulse signal, then the
transmitted gas velocity value and finally the transmitted flow rate.
6 TB-990101B 23/27.73+
Minimum Automatic Gain Control (AGC) Ratio ⎯ The flow computer

calculates the AGC ratio for each ultrasonic path in both path directions. An alarm
Difference Between
will occur if the AGC ration of any path drops below this ratio. Reasonable entries
‘Gas Velocity’ and
are 1.5 to 2.
‘Velocity of Sound’
Minimum Percent Sample Ratio ⎯ This entry checks the ratio of good
The ‘gas velocity’ through received data pulses verses total transmitted pulses for each ultrasonic path in
the meter tube is directly
proportional to the actual
both directions. A ratio below this setting will cause an alarm. Reasonable entries
flow rate of the gas in the are 50% to 70%.
pipeline. The ‘velocity of Velocity of Sound (VOS) in Gas Deviation Percent ⎯ In some
sound’ (VOS) refers to the
configurations, the flow computer can verify that the average VOS calculated for
amount of time it takes a
transmitted acoustic pulse all paths agrees with the VOS of each individual path. This entry is the maximum
to travel through the gas percent that any one path VOS varies from the average VOS of all the paths.
ultrasonic paths. The VOS Gas Velocity Low Cutoff ⎯ Some gas movement can occur even when an
will vary depending upon
ultrasonic meter is blocked-in. This is caused by convection currents within the
gas quality and flowing
conditions. meter tube. Enter a minimum gas velocity, in feet per second (Revision 23) or
meters per second (Revision 27), below which you do not want to totalize. Consult
with Instromet to determine this value.
Flow Computer Database Addresses and

Index Numbers
The following tables list the Modbus database addresses within the OMNI have
been assigned to the Q-Sonic ultrasonic metering feature. These tables are
categorized per data type.
Meter Run Alarm Status Points ⎯ Real Time Data

Database Address Database Address
Description for Meter Run Number Description for Meter Run Number
1 2 3 4 1 2 3 4
Loss of communication 2154 2254 2354 2454 Path 1 - sample error alarm 2167 2267 2367 2467
Loss of pulse impulse 2155 2255 2355 2455 Path 2 - sample error alarm 2168 2268 2368 2468
Flow rate delta alarm 2156 2256 2356 2456 Path 3 - sample error alarm 2169 2269 2369 2469
Path 1a - AGC ratio alarm 2157 2257 2357 2457 Path 4 - sample error alarm 2170 2270 2370 2470
Path 1b - AGC ratio alarm 2158 2258 2358 2458 Path 5 - sample error alarm 2171 2271 2371 2471
Path 2a - AGC ratio alarm 2159 2259 2359 2459 Overall sample error alarm 2172 2272 2372 2472
Path 2b - AGC ratio alarm 2160 2260 2360 2460 Path 1 - gas VOS alarm 2173 2273 2373 2473
Path 3a - AGC ratio alarm 2161 2261 2361 2461 Path 2 - gas VOS alarm 2174 2274 2374 2474
Path 4a - AGC ratio alarm 2163 2263 2363 2463 Path 4 - gas VOS alarm 2176 2276 2376 2476
Path 5a - AGC ratio alarm 2165 2265 2365 2465 Notes: AGC Î Automatic Gain Control
Path 5b - AGC ratio alarm 2166 2266 2366 2466 VOS Î Velocity of Sound
TB-990101B 23/27.73+ 7
16-bit Integer Registers ⎯ Real Time Data

1 2 3 4 1 2 3 4
Flow direction (0=frwd,1=rvrs) 3155 3255 3355 3455 Path 1a - AGC level 3180 3280 3380 3480
Path 1 - performance (%)* 3158 3258 3358 3458 Path 1b - AGC level 3181 3281 3381 3481
Path 2 - performance (%)* 3159 3259 3359 3459 Path 2a - AGC level 3182 3282 3382 3482
Path 4 - performance (%)* 3161 3261 3361 3461 Path 3a - AGC level 3184 3284 3384 3484
Path 1a - AGC ratio* 3163 3263 3363 3463 Path 4a - AGC level 3186 3286 3386 3486
Path 1b - AGC ratio* 3164 3264 3364 3464 Path 4b - AGC level 3187 3287 3387 3487
Path 2a - AGC ratio* 3165 3265 3365 3465 Path 5a - AGC level 3188 3288 3388 3488
Path 2b - AGC ratio* 3166 3266 3366 3466 Path 5b - AGC level 3189 3289 3389 3489
Path 3a - AGC ratio* 3167 3267 3367 3467 Path 1a - AGC limit 3190 3290 3390 3490
Path 3b - AGC ratio* 3168 3268 3368 3468 Path 1b - AGC limit 3191 3291 3391 3491
Number of paths 3173 3273 3373 3473 Path 4a - AGC limit 3196 3296 3396 3496
Number of samples taken 3174 3274 3374 3474 Path 4b - AGC limit 3197 3297 3397 3497
Path 1 - valid sample 3175 3275 3375 3475 Path 5a - AGC limit 3198 3298 3398 3498
Path 2 - valid sample 3176 3276 3376 3476 Path 5b - AGC limit 3199 3299 3399 3499
Path 3 - valid sample 3177 3277 3377 3477
Path 4 - valid sample 3178 3278 3378 3478 Notes: AGC Î Automatic Gain Control
Path 5 - valid sample 3179 3279 3379 3479
* Integer with two inferred decimal places.
32-bit IEEE Floating Points ⎯ Real Time Data
1 2 3 4 1 2 3 4
Maximum flow deviation (%) 17513 17613 17713 17813 Path 1 - velocity of sound 17527 17627 17727 17827
Minimum AGC ratio (1 to 10) 17514 17614 17714 17814 Path 2 - velocity of sound 17528 17628 17728 17828
Minimum sample ratio (%) 17515 17615 17715 17815 Path 3 - velocity of sound 17529 17629 17729 17829
Max. VOS deviation (%) 17516 17616 17716 17816 Path 4 - velocity of sound 17530 17630 17730 17830
Gas velocity low cutoff 17517 17617 17717 17817 Path 5 - velocity of sound 17531 17631 17731 17831
Avg. path performance (%) 17520 17620 17720 17820 Path 1 - gas velocity 17532 17632 17732 17832
Velocity of sound (VOS) 17521 17621 17721 17821 Path 2 - gas velocity 17533 17633 17733 17833
Gas velocity 17522 17622 17722 17822 Path 3 - gas velocity 17534 17634 17734 17834
Pressure 17523 17623 17723 17823 Path 4 - gas velocity 17535 17635 17735 17835
Temperature 17524 17624 17724 17824 Path 5 - gas velocity 17536 17636 17736 17836
Gas flow rate 17525 17625 17725 17825 Notes: AGC Î Automatic Gain Control
Net flow rate 17526 17626 17726 17826 VOS Î Velocity of Sound
8 TB-990101B 23/27.73+
32-bit IEEE Floating Points 32-bit IEEE Floating Points

Previous Hour’s Average Data Previous Day’s Average Data
1 2 3 4 1 2 3 4
Number of samples taken 17537 17637 17737 17837 Number of samples taken 17568 17668 17768 17868
Path 1 - valid sample 17538 17638 17738 17838 Path 1 - valid sample 17569 17669 17769 17869
Path 1a - AGC level 17543 17643 17743 17843 Path 1a - AGC level 17574 17674 17774 17874
Path 1b - AGC level 17544 17644 17744 17844 Path 1b - AGC level 17575 17675 17775 17875
Path 1a - AGC limit 17553 17663 17773 17883 Path 1a - AGC limit 17584 17684 17784 17884
Path 1b - AGC limit 17554 17664 17774 17884 Path 1b - AGC limit 17585 17685 17785 17885
Path 1 - gas velocity 17563 17663 17763 17863 Path 1 - gas velocity 17594 17694 17794 17894
Notes: AGC Î Automatic Gain Control
TB-990101B 23/27.73+ 9
Flow Computer Configuration Data ⎯ Miscellaneous Meter Run Configuration

1 2 3 4 1 2 3 4
Flowmeter device type 3108 3208 3308 3408 Primary Measurement 3157 3257 3357 3457
Source (0=Serial, 1=Pulses)
SV module port # 3153 3253 3353 3453 Flow pulse freq. I/O point # 13001 13014 13027 13040
Flow direction (0=frwd,1=rvrs) 3155 3255 3355 3455
Flow Computer Configuration Data ⎯ Meter Run Setup

1 2 3 4 1 2 3 4
Tube diameter 7145 7245 7345 7445 Minimum AGC ratio (1 to 10) 17514 17614 17714 17814
Tube coefficient 7146 7246 7346 7446 Minimum sample ratio (%) 17515 17615 17715 17815
Tube reference temperature 7147 7247 7347 7447 Max. VOS deviation (%) 17516 17616 17716 17816
Maximum flow deviation (%) 17513 17613 17713 17813 Gas velocity low cutoff 17517 17617 17717 17817
Flow Computer User Displays

SV Module Serial Communications Port
You can view live data received via RS-485 communications on the flow
computer front panel LCD display only if a SV port is used to input the RS-485
interface from the Q-Sonic flowmeter. To view this data, press [Setup] [n]
[Display] on the OMNI front panel keypad (where “n” equals the SV port
number, 1 to 4, you want to display) when in the Display Mode. The following
data will display:
SV PORT 1 Q-SONIC
Transaction
12345
V-Status
0
C/R Status
0
# of Paths
3
# of Samples
20
#1 ValSample
19
#2 ValSample
19
#3 ValSample
18
1a(Sw)AgcLevel
35123
10 TB-990101B 23/27.73+
1b(Sw)AgcLevel
27566
2a(Ax)AgcLevel
37521
2b(Ax)AgcLevel
29912
3a(Sw)AgcLevel
35976
3b(Sw)AgcLevel
26133
1a(Sw)AgcLimit
65535
1b(Sw)AgcLimit
65535
2a(Ax)AgcLimit
65535
2b(Ax)AgcLimit
65535
3a(Sw)AgcLimit
65535
3b(Sw)AgcLimit
65535
V-Sound
351.13
Gas Vel
2.175
Pres kPa
9.9990E+09
T Deg.K
9.9990E+09
am3/Hr
1.6725
nm3/Hr
9.9990E+09
Stability
3
#1V-Sound
320.45
#2V-Sound
352.56
#3V-Sound
352.17
#1GasVel
2.13
#2GasVel
2.21
#3GasVel
2.15
TB-990101B 23/27.73+ 11
Meter Run Data

To view the meter run data on the flow computer LCD display, press [Meter] [n]
[Display] on the OMNI front panel keypad (where “n” equals the meter run
number, 1 to 4, you want to display) when in the Display Mode. The following
data will display:
METER #1 Q-SONIC
Performance%
100.00
VOSm/s
352.137
Gas Vel
2.135
Flow m3/hr
1.625
Sistematic swirl
#1 Perform %
100.00
#2 Perform %
100.00
#3 Perform %
100.00
#1a Ratio
1.5
#1b Ratio
1.6
#2a Ratio
1.7
#2b Ratio
1.8
#3a Ratio
1.5
#3b Ratio
1.7
12 TB-990101B 23/27.73+
OMNI Flow Computers, Inc.
Date: 04 Dec '07 Author(s): SEF Version: TB-020101H
OMNI Serial/Ether net-Modbus Mux Module

Model 68-6209: Setup & Installation
Contents
Scope .....................................................................................................3
supplements the information Abstract .................................................................................................3
contained in the User
Manual, applicable to all Features and Specifications.................................................................3
OMNI flow computer
firmware revisions. Modbus Support....................................................................................4
Installation .............................................................................................4
OMNI Serial/Ethernet-
Modbus Mux Module
Quick Installation Reference............................................................................. 4
68-6209: Jumper Settings ................................................................................................. 6
Setup & Installation Address Selection.............................................................................................. 7
All OMNI 3000/6000 flow IRQ Selection.................................................................................................... 7
computers provide optional
10BaseT Ethernet capability Channel Selection ............................................................................................. 7
via OMNI’s proprietary
communication module
Termination Selection ....................................................................................... 8
model 68-6209. Wiring ............................................................................................................... 8
LED Indicators.......................................................................................9
Getting Tech Support
RS-232/RS-485 ................................................................................................. 9
OMNI Technical support is
available at: Ethernet ............................................................................................................. 9
Phone: (281) 240-6161 Repeater .......................................................................................................... 10
Fax: (281) 240-6162 Configuration.......................................................................................10
Technical information is OMNI 3000/6000............................................................................................ 10
available on our website at: Modbus Mux (Multiplexer) ............................................................................ 11
www.omniflow.com
Setting an IP address ....................................................................................... 12
Or send email to:
Configuration Menus ...................................................................................... 14
helpdesk@omniflow.com
Configuration Options Menu .......................................................................... 15
Ethernet Parameters Menu .............................................................................. 15
Host Parameters Menu .................................................................................... 17
Repeater Parameters Menu ............................................................................. 19
Security Parameters Menu .............................................................................. 21
System Information Menu .............................................................................. 23
Advanced Parameters Menu ........................................................................... 24
Logging Parameters Menu .............................................................................. 25
Debug Options Menu ...................................................................................... 26
TB-020101H  All Revisions 1

Appendix A: Communicating Across Subnets ................................ 28

Appendix B: Example Syslog Messages.......................................... 29
Appendix C: Network Printing Error Codes ..................................... 31
Appendix D: Setting a Temporary IP Address for older versions of
OMNI SE Firmware.............................................................................. 32
Appendix E: Using OmniCom for DOS over TCP/IP ........................ 34
Windows NT/2000.......................................................................................... 34
Windows 95/98 ............................................................................................... 34
SE Firmware Revision History ........................................................... 35

TB-020101H OMNI Serial/Modbus Mux Module 68-6209: Setup & Installation
Scope
This technical bulletin applies to all firmware revisions of OMNI 3000/6000
flow computers.
Abstract
OMNI Flow Computers manufactures a communications module that provides
10BaseT Ethernet capability to existing 3000/6000 flow computers. The
module model currently produced is:
68-6209 Serial/Ethernet-Modbus Mux (SE) Module
The SE Module provides two communications channels. One channel is an RS-

232/RS-485 Serial channel and the other is a 10BaseT Ethernet channel.
Features and Specifications

Ethernet Printing The OMNI SE Module provides one RS-232/RS-485 port, one 10BaseT
Ethernet printing was Ethernet port, one 2-wire RS-485 Repeater port and one RS-232 Configuration
introduced in v1.50 of the Port. The board can be used with existing OMNI 3000/6000 flow computers
SE module firmware. To with no additional firmware modifications required. Address selection for Serial
determine if your flow
computer firmware supports Module #1 (S1), Serial Module #2 (S2) or Serial Module #3 (S3) is provided
Ethernet printing, press along with the ability to swap the Serial and Ethernet channels. For OMNI
STATUS DISPLAY on the
firmware versions less than vXX.74.10, this is achieved by the Ethernet port
“emulating” a serial port.
front panel of the flow
computer. If the display
shows an SE module
address and in addition The RS-232/RS-485 Serial port is hardware identical to one half the OMNI RS-
shows the firmware of the
SE module (v1.50+), your 232-C/RS-485 Serial I/O Module model #68-6205-B and maintains the same I/O
flow computer firmware connector pin-out and specifications. It can be configured for RS-232, 4-wire
supports Ethernet printing. RS-485 or 2-wire RS-485 communications. The serial port signals always
All reports are still sent to
the local RS-232 serial port occupy contacts 1 through 6 of the back-panel terminal strip (see OMNI
printer if one is configured. Technical Bulletin TB-980503 for additional information).
See the OmniCom for
Windows v1.25+ program
Help file content under the
The Ethernet port supports encapsulated Modbus in ASCII or RTU format,
Configure/Ports menu Modbus/TCP and remote configuration via Telnet. Ethernet signals always
settings for additional occupy contacts 7 through 12 of the back-panel terminal strip. Up to four
details on configuring
Ethernet printing. simultaneous connections are supported along with one Telnet connection.
Ethernet/Serial The Repeater port allows messages arriving via the Ethernet connections to be
Terminal Assignments routed to additional flow computers or compatible Modbus devices, using a
Ethernet and serial signals multi-dropped 2-wire RS-485 communication link. Messages are routed to the
have fixed terminal
assignments, even when
Repeater port when they are not addressed to the Host flow computer.
the function of the two are
swapped. Serial signals The flow computer containing the SE Module is referred to as the Host. All
always correspond to transactions containing the Modbus ID of the Host are routed internally to the
terminals 1 through 6 and
Ethernet signals always hosting flow computer while all others are routed out the Repeater port. The
correspond to terminals 7 Host and Repeater Ports can be accessed simultaneously with complete overlap
through 12 of the OMNI
backpanel terminal strip.

of the I/O. The communication parameters, such as baud rate or protocol, do not
need to be the same for the Host and Repeater ports.
The onboard RS-232 configuration port (DB9 connector) allows local
configuration of the SE Module’s parameters using Telnet protocol and a
terminal emulator program such as Microsoft ® HyperTerminal.
Modbus Support
Modbus/TCP Standard Modbus messages encapsulated in TCP/IP are supported in either RTU
More information about the
or ASCII format and they may be intermixed. The messages will be converted
enhanced Modbus protocol based upon configuration parameters in the SE module. Modbus IDs are used to
for TCP communications is determine how the messages are routed. If the address matches the one
available on the Web at:
configured in the Host port parameters, it is routed to the Host port. Otherwise,
www.modbus.org it is routed out the Repeater port. The SE Module also supports Modbus/TCP,
which is an enhanced Modbus protocol used specifically for TCP
communications. The protocol you use depends on the driver supported in your
application program.
Installation
You can install the SE Module in any slot in the flow computer. The slot in
which you install the module determines which backpanel terminal strip is used
for the signals.
Quick Installation Reference

Follow these steps to install and configure the SE module.
 Decide which OMNI “serial port” you wish the Ethernet module to
occupy.
 Set the Address, channel selection, and IRQ jumpers on the SE module.
 Write down the six hex digits on the white label on the small plug in card
on the board. This is the last part of the MAC or hardware address of the
Ethernet module. The first part of the MAC address is always 0090C2
and is not shown on the label.
 Set the termination resistors for the RS232/485 serial port for the desired
mode.
 Install the Repeater port termination jumpers if it will be the first or last
device on the 485 link.
 Install the module in the flow computer.

 Connect the supplied 10BaseT cable to the terminal strip on the back of
the flow computer that matches the slot occupied by the SE module.
 Connect the 10BaseT cable to an active network and apply power to the
flow computer. The green Ethernet LNK LED should go active. If there
is network activity, the red Ethernet ACT LED will flash.
 Set the parameters for the Ethernet port in the flow computer to match the
default Host parameters in the SE module. If you change the default Host
parameters in the SE module config, you must also change the parameters
for the Ethernet port of the flow computer to match the Host parameters
set in the SE module’s config.
 Configure the SE module using OmniCom (SE Module firmware v1.50
and up and certain versions of OMNI firmware), a Telnet connection (we
recommend OMNI’s ‘Network Utility’ program which can be installed
from the OMNI website or from the OmniCom install CD) or by
connecting a PC to the SE module using a nine-pin straight through serial
cable plugged into the on-board configuration port (DB9 connector).
 Set the IP address, Subnet Mask and Gateway for the SE module. Make
sure to save the parameters before proceeding.
 Go through the SE module’s configuration menus and make any other
parameter changes desired. All “Host” parameters must match the
parameters of the associated Ethernet port of the flow computer.

Jumper Settings
Figure 1 is a drawing of the OMNI SE Module. The jumper and termination
resistor pack locations are magnified.
JB1 JB2 JB3
-RS485- 232/485
RS485 2WIRE UNTERMINATED
232/485
-RS232- RS485
232/485 4WIRE TERMINATED
232 / 485
ETHERNET
REPEATER
GRN
GRN
GRN
RED
RED
RED
232/485=A
232/485=B
JP3 JP2
ADDRESS
A1 S1 S2 S3
JUMPER
A1 OUT IN OUT REPEATER

A2 A2 OUT OUT IN TERMINATION
2 3
IRQ
Figure 1. The OMNI Serial/Ethernet-Modbus Mux (SE) Module Model

68-6209 showing jumper and termination resistor pack
locations.

Address Selection
Depending on the model and firmware revision, OMNI flow computers can have
up to three Serial I/O modules installed. Each Serial I/O module provides two
channels, for a maximum total of six Serial I/O communication channels. Note:
although logical addressability exists for three SE modules in the system,
existing OMNI 6000 system power requirements mandate a maximum of two SE
modules. This still provides 4 virtual hosts per Ethernet port. Jumper settings
on the SE Module select the module address as S1, S2 or S3 (see table below).
Jumper Settings for

Serial Module Address Selection
Module Address
Jumper S1 S2 S3
A1 OUT IN OUT
A2 OUT OUT IN
IRQ Selection
A jumper is provided for selecting the interrupt request (IRQ) level of the
module. IRQ level 2 or 3 can be selected. The jumper should be configured to
use IRQ level 2, unless an SV module is installed in the flow computer. Use
IRQ level 3 if an SV combo card is installed.
Channel Selection
An onboard jumper determines which “position” the Serial and Ethernet
channels occupy. If the Serial (RS-232/RS-485) is selected as port A the
Ethernet will be port B. If the Serial channel is selected as port B, then the
Ethernet channel will be port A. This allows the Ethernet channel to occupy any
serial position and work with other communication requirements of the flow
computer. If the module is selected as S1 and a printer is required on serial port
1, then RS-232/RS-485 should be selected for port A and Ethernet for port B.
The standard (default) port assignment for RS-232/RS-485 is PORT-A and
Ethernet is Port-B. These can be swapped by moving the jumper from position
RS-232/RS-485-A to RS-232/RS-485-B.
Port Numbers Assigned to SE Module Addresses and Channels
Module
RS-232/RS-485
Address Channel Selection Modbus Mux Port #
Serial Port #
Selection
S1 RS-232/RS-485 = A 1 2
S1 RS-232/RS-485 = B 2 1
S2 RS-232/RS-485 = A 3 4
S2 RS-232/RS-485 = B 4 3
S3 RS-232/RS-485 = A 5 6
S3 RS-232/RS-485 = B 6 5

Termination Selection
Placement of resistor packs determines the serial wiring and termination of the
serial port. These are set according to the table below. Jumpers JP2 and JP3
provide termination for the repeater port.
Termination Resistor Pack Placement for Serial Port Configuration

Termination Resistor Packs
Serial Port JB1 JB2 JB3
Configuration Position Position Position
RS-232/RS-485, RS-232/RS-485
RS-232 RS-232
4-Wire Unterminated
RS-485, 2-Wire, RS-485
RS-485 RS-485, 2-Wire
RS-485, 2-Wire, RS-232/RS-485
RS-485 RS-485, 2-Wire
Unterminated Unterminated
RS-485, 4-Wire, RS-232/RS-485, RS-485
RS-485
Terminated 4-Wire Terminated
RS-485, 4-Wire, RS-232/RS-485, RS-232/RS-485
RS-485
Unterminated 4-Wire Unterminated
Wiring
Ethernet/Serial The connections for the RS-232/RS-485 serial port always occupy contacts 1
Terminal Assignments through 6 of the appropriate OMNI back-panel terminal strip (see table below).
Ethernet and serial port This is regardless of it being selected as port A or port B.
connections have fixed
terminal assignments,
regardless of which serial
port channel you select.
OMNI Flow Computer Terminal Assignments for Serial Pinout
Serial signals always Terminal RS-232 RS-485 4-Wire RS-485 2-Wire
1 TX TX-B TX/RX-B
correspond to terminals 1
through 6 and Ethernet
signals always correspond 2 TERM  
to terminals 7 through 12 of 3 RX RX-B 
4 GND (Return) GND (Return) GND (Return)
the OMNI backpanel
terminal strip.
5 RTS (Key Txmit) TX-A TX/RX-A
6 RDY (Ready) RX-A 
The Ethernet (10BaseT) and repeater ports always use terminals 7 through 12 of
the OMNI back-panel (see table below). A 10BaseT Ethernet cable is provided
for connection to the back-panel. One end is terminated for attaching to the
3000/6000 terminal blocks and the other end has an RJ45 jack. Care should be
taken on the terminal end to keep the + and - wires for TX and RX twisted
together as close to the terminal contacts as possible.

OMNI Flow Computer Terminal Assignments

for Ethernet Pinout
Terminal Signal 10BaseT Cable Color
7 TX- Orange (Orange/White)
8 TX+ White/Orange
9 TX/RX-B (Repeater) 
10 TX/RX-A (Repeater) 
11 RX- Green (Green/White)
12 RX+ White/Green
LED Indicators
Figure 2 is a side view of the SE module showing the LED indicators.
Figure 2. LED indicators of the OMNI Serial/Ethernet-Modbus Mux

(SE) Module Model 68-6209.
RS-232/RS-485
RTS (red) : Request to Send. Active when the serial port transmitter is
enabled for sending data.
TX (red) : Transmit Data. Active when data is being transmitted by
the serial port.
RDY (green) : Ready. Used for printers. Active when the device is ready.
RX (green) : Receive Data. Active when data is being received.
Ethernet
ACT (red) : Activity. Active when network activity is detected. Should
flash intermittently as data packets are detected on the
network. They do not have to be destined for the SE
Module.
TX (red) : Transmit Data. Active when the Host port is sending data
back to a network connection.

LNK (green) : Link. Active when a valid 10BaseT network is detected.

This should always be on when connected to a network.
RX (green) : Receive Data. Active when the Host port is receiving data
from a network connection.
Repeater
RTS (red) : Request to Send. Active when the Repeater transmitter is
enabled for sending data.
TX (red) : Transmit Data. Active when data is being transmitted by
the Repeater port.
REN (green) : Receive Enable. Active when the Repeater’s receiver is
enabled.
RX (green) : Receive Data. Active when data is being received by the
Repeater port.
Configuration
No flow computer firmware changes are necessary to use the SE Module in the
OMNI 3000/6000. However, configuration entries are needed in the flow
computer and in the Modbus Mux portion of the SE module. These
configuration parameters must match for proper operation.
If you intend to install two SE modules in a fully loaded 6000, you should
consult with the factory to verify PSU requirements. Although logical
addressability exists for three SE modules in the system, existing OMNI 6000
system power requirements mandate a maximum of two SE modules. This still
provides 4 virtual hosts per Ethernet port.
OMNI 3000/6000
In the OMNI 3000 or 6000 flow computer, configuration parameters should be
entered for the serial ports that the module channels occupy. The serial port
numbers depend upon the address and channel selections made on the SE
Module.
Port Numbers Assigned to SE Module Addresses and Channels

Module
RS-232/RS-485
Address Channel Selection Modbus Mux Port #
Serial Port #
Selection
S1 RS-232/RS-485 = A 1 2
S1 RS-232/RS-485 = B 2 1
S2 RS-232/RS-485 = A 3 4
S2 RS-232/RS-485 = B 4 3
S3 RS-232/RS-485 = A 5 6

S3 RS-232/RS-485 = B 6 5
The parameters for the serial port where the RS-232/RS-485 port resides should
be made according to the intended application for that port.
The parameters for the Ethernet/serial port where the Modbus Mux resides need
to match parameters entered within the Modbus Mux module.
The recommended settings are:
Recommended Modbus Mux

Ethernet Port Settings for
OMNI Firmware vXX.74.10 and up
SE Firmware > 2.0 No
(may not be
displayed)
Modbus ID 1
Modicon Yes / No
Compatible (according to your
application)
Recommended Modbus Mux

Serial Port Settings for
OMNI Firmware below vXX.74.10
Baud Rate 38400
Data Bits 8
Stop Bits 1
Parity None
Xmit Key Delay 0
Modbus ID 1
Modbus Type 0 (RTU)
Modicon Yes / No
Compatible (according to your
application)
CRC Enabled Yes
Modbus Mux (Multiplexer)

The Modbus Mux is that part of the SE module that allows up to 4 Modbus
Masters to communicate simultaneously to the flow computer using separate
TCP socket connections. The Modbus Mux has a separate set of configuration
parameters stored in Flash memory on the SE module. These parameters must
be set before the module can operate properly.
The configuration parameters can be changed using OMNI’s OmniCom
software v1.25 and up with SE Module firmware v1.50 and up and the OMNI

flow computer firmware supports SE Module configuration. You may also

configure remotely via Ethernet using any Telnet application (we recommend
using OMNI’s Network Utility which can be installed from the OMNI website
or from the OmniCom install CD) or a terminal emulator such as Microsoft ®
HyperTerminal through the on-board DB9 connector/serial port. An inactivity
time out of 5 minutes is imposed for both the Serial and Telnet connections. If
no input is received over the time out period, any non-saved parameter changes
will be discarded and the password prompt will be displayed.
The on board serial port is configured for 9600 baud, 8 bits, 1 stop bit and no
parity. A standard RS-232, 9-pin serial cable can be connected directly from a
PC to the board. A NULL Modem cable is not required.
A separate password may be configured for the serial port, and Ethernet Telnet
access. The default password is “omni”. Remote configuration access may be
disabled by setting the Telnet port number to zero.
Before the Modbus Mux can be used, its IP address needs to be set to a value
that is compatible with the network you are using. As shipped, the IP address
defaults to 10.0.0.1. The IP address can be changed via the front panel of the
OMNI flow computer for certain versions of the OMNI firmware, via Ethernet
using the OMNI Network Utility program, or via the on-board serial port
connection.
Setting an IP address
MAC and IP Addresses Determine your MAC address. The MAC address is a 48 bit number made up of
The MAC address and IP a three byte manufacturer ID and a three byte device ID. The manufacturer ID
address used here are for for the SE module is always 0090C2 and the device ID can be found on a white
example purposes only.
You must use the MAC
label on the SE module. To find the device ID, look for a small plug-in board
address from your SE on the bottom right of the SE Module (DIN connector bottom left). On this card
Module and the IP address is a small white label with bar codes and a six-digit hex number. This is the
you have selected for your
network. device ID. The MAC address is usually expressed by grouping the digits by two
and placing a dash between them. If the device ID is C02D3F, then the MAC
MAC Address for Unix address will be:
Systems
The example shown is for
00-90-C2-C0-2D-3F
Microsoft Windows. On a
Unix system, the MAC
address is typed as Note: The example shown is for Microsoft Windows. On a Unix system the
00:90:C2:C0:2D:3F.
MAC address is typed as 00:90:C2:C0:2D:3F.
The following method uses the Network Utility program on a PC that is

connected to the same network as the flow computer with the SE module
installed. The MAC address you use will be the one from your module and the
IP will be what you have selected for your network.
For additional information on Network Utility, see the help in PDF format or by
pressing F1 when the program is running.

 Start up the Network Utility. A list is shown of all the OMNI SE Ethernet
modules installed on the network.
 Find the MAC address from your module in the MAC Address column of
the display. It should have IP Address 10.0.0.1 (factory default).
 Click on the row with your MAC address and select “Set IP” from the
menu. Enter the IP Address you have selected for your network at the
prompt (for example: 200.100.101.235).
 Network Utility automatically pings the address entered to be sure it is not
in use by another device. The box below the list displays the status of the
pings. There should be time outs received for the pings. If you receive
any replies then that address is in use and another one should be chosen.
 If the address is not in use, Network Utility prompts you for a password.
Enter “omni” and press return.

 The list of OMNI SE Ethernet Modules installed on the network is

refreshed and you should see your MAC address with the new IP Address
entered in the list.
 Click on the row with your module and select Configure from the menu.
Set the Subnet Mask and Gateway. Save the parameters. Any other
parameters may be changed and saved at this time.
Configuration Menus
The menus displayed are identical for serial or Telnet configuration (see Figure
3). The menu is divided into two halves. The left hand pane shows the main
Configuration Options and the right hand pane shows the current submenu. The
submenu displayed will depend on which number is selected from the
configuration options. Items in the submenu can be selected by entering one of
the letters. The submenu selections are not case sensitive and will accept upper
or lower case.
When entering a parameter, pressing escape will abort the entry and leave the
parameter unchanged.
The parameters displayed are a copy of the actual System Parameters.

No changes take place until the parameters are saved by selecting *.
Figure 3. Configuration menu of the OMNI Modbus Mux Module.

Configuration Options Menu

Version Numbers (v)
The version number (v) that Submenu Selection
appears in the top right of
the configuration menus is Entering a number in the range of 1 through 5 will select one of the submenus
the OMNI SE firmware for display in the right hand pane of the configuration menu.
version. The actual version
number of your module may
be more recent than the one
that appears in the figures Save Configuration (*)
of this document, which at
the time of its release was Saves the currently displayed parameters to the System Parameters and re-
v1.24. initializes the hardware and software affected by the changes. Some parameter
changes may cause connections to be dropped including the current Telnet
session. For example, if the IP address is changed all connections will be
dropped and the new IP address made active. If connected via Telnet the
connection will need to be re-established using the new IP address.
Cancel Changes & Reload (%)

Cancels any changes made and reloads the current active set of parameters. Any
parameter changes made without saving will be lost. All submenu parameters
will be reloaded, not just the submenu currently displayed.
Set Factory Defaults (#)

Reloads all parameters with the defaults set at the factory. All submenu
parameters will be set to defaults, not just the submenu currently displayed.
Board Reset ($)

Resets the OMNI SE module. It does not reset the OMNI 3000/6000.
Refresh Menu (?)

Re-displays the current selections.
Exit (!)
Disconnects and terminates the configuration session. If the parameters have
been changed during the configuration session, but have not been saved, a
reminder message is displayed..
Ethernet Parameters Menu

Selecting Configuration Option 1 displays the Ethernet Parameters Submenu
(Figure 4). Entering one of the option letters will allow the parameter to be
changed.
TCP/IP destination endpoints are referred to as “ports” and are entered as
decimal numbers.

Figure 4. Ethernet Parameters Submenu of the OMNI Modbus Mux

Module.
IP Address
All devices on a network require a unique IP address. This is the static IP
address used for all network connections to the Modbus Mux. The IP address is
entered in dotted decimal notation. The default is 10.0.0.1.
Subnet Mask
IP addresses contain a Network Identifier (netid), a Subnet Identifier (subnetid),
and a Host Identifier (hostid). Subnet masks identify the portion of the address
occupied by the netid and the subnetid. The Subnet Mask is entered in dotted
decimal notation. The default is 255.0.0.0.
Gateway
If a gateway exists for accessing other subnets, it can be entered here. The
Gateway is entered in dotted decimal notation. The default is 0.0.0.0 or
disabled.
Eth ID
A 15 character ID that can be used to name or describe the SE Module in an
OMNI.
Encap. Modbus Port

TCP/IP port number used to communicate with the flow computer using
standard Modbus encapsulated by TCP/IP. It may be changed to meet any

special needs of your network. Entering 0 for the port number will disable
Modbus connections. This port number must be different from the Modbus/TCP
port number. The default is 6000.
Modbus/TCP Port
TCP/IP port number used to communicate with the flow computer using
Modbus/TCP. The default is the standard Modbus/TCP port of 502. It may be
changed to meet any special needs of your network. Entering 0 for the port
number will disable Modbus/TCP connections. This port number must be
different from the Modbus port number.
Telnet Port
Port number used for Telnet connections. The default is the standard Telnet port
of 23. It may be changed to meet any special needs of your network. Entering 0
for the Telnet port will disable Telnet connections and configuration changes
can then only be made through the onboard DB9 serial port default or via
Network Utility v1.07 and up which gives you a chance to reset the Telnet Port
to the default of 23.
Message Time Out

This is the time in milliseconds that the Modbus Mux will wait for a complete
message on the TCP connection. It should be long enough to account for any
network delays but shorter than the retry time out in any application software
used for communications. The default is 1000 milliseconds (1 second).
Inactivity
This is the time in minutes that a connection to the Encapsulated Modbus and
Modbus/TCP ports can remain idle before being disconnected. The default is 15
minutes. Entering 0 will disable the Inactivity time out. Note: This setting does
not apply to the time out for idle Telnet connections, which is fixed at 5 minutes.
Host Parameters Menu

Selecting Configuration Option 2 displays the Host Parameters Submenu
changed.
The Host refers to the flow computer in which the Modbus Mux is installed.
These parameters should match the configuration parameters in the OMNI for
the port the Ethernet channel occupies.

Figure 5. Host Parameters Submenu of the OMNI Modbus Mux

Module.
Baud Rate
Baud rate configured for the serial port in the OMNI. It can be set to 19200 or
38400 depending on other system requirements. The Default is 38400 and is the
recommended setting. Note: The baud rates of 19200 and 38400 are mutually
exclusive for the RS-232/RS-485 port and the Host port. If the Host is set to
38400 then 19200 cannot be used on the RS-232/RS-485 port. (Note: for OMNI
firmware vXX.74.10 and above, the baud rate is not configurable in the OMNI
and is defaulted to 38400 baud for the Ethernet port. If your OMNI SE module
is installed in an OMNI with this firmware, please set the Host Baud Rate to
38400.)
Data Bits
Data bits can be selected for 7 or 8 data bits. This must match the corresponding
parameter in the OMNI. The default is 8 and is the recommended setting.
(Note: for OMNI firmware vXX.74.10 and above, the data bits setting is not
configurable in the OMNI and is defaulted to 8 for the Ethernet port. If your
OMNI SE module is installed in an OMNI with this firmware, please set the
Data Bits to 8.)
Stop Bits
The Stop Bits can be selected for 1 or 2. If two stop Bits are selected the parity
will be set to none. This must match the corresponding parameter in the OMNI.
The default is 1 and is the recommended setting. (Note: for OMNI firmware
vXX.74.10 and above, the stop bits setting is not configurable in the OMNI and

is defaulted to 1 for the Ethernet port. If your OMNI SE module is installed in

an OMNI with this firmware, please set the Stop Bits to 1.)
Parity
The parity may be selected to be None, Even or Odd. Even and Odd Parity can
be used only with 1 Stop Bit. This must match the corresponding parameter in
the OMNI. The default is None and is the recommended setting. (Note: for
OMNI firmware vXX.74.10 and above, the parity is not configurable in the
OMNI and is defaulted to None for the Ethernet port. If your OMNI SE module
is installed in an OMNI with this firmware, please set the Parity to None.)
Modbus ID
Modbus ID of the Host serial port. It is used to determine if messages are sent
to the Host or sent out the Repeater port. It must match the corresponding
parameter in the OMNI for proper operation. The default is 1. It can be
changed to any valid Modbus ID. This address will not be accessible on the
Repeater port.
Protocol
This is the protocol expected by the host serial port. It can be set to Modbus
RTU or Modbus ASCII. It does not determine what protocol is used over
TCP/IP. The messages will be converted if required. It must match the
corresponding parameter in the OMNI. The default is Modbus RTU and it is the
recommended setting.
Initial Delay
This is the time in milliseconds that will be waited for a response from the
OMNI before freeing up the TCP port for other connections. The default is 200
ms and it is the recommended setting.
Char Delay
This is the time in milliseconds that will be waited between characters from the
OMNI before freeing up the TCP port for other connections. The default is
20ms and it is the recommended setting.
Repeater Parameters Menu

Selecting Configuration Option 3 displays the Repeater Parameters Submenu
changed.
The Repeater port is used to ‘extend’ the Ethernet connections to other OMNI
flow computers or compatible Modbus devices using a 2-wire multi-dropped
RS-485 connection.

Any transaction that is destined for a Modbus ID that does not match the Host
flow computer configuration is routed out the Repeater port.
Figure 6. Repeater Parameters Submenu of the OMNI Modbus Mux

Module.
Baud Rate
Baud rate used by the repeater port. The choices are 9600, 19200, 38400 and
57600. It should be set as high as possible. The default is 38400.
Data Bits
The Repeater port can be selected for 7 or 8 data bits. The default is 8.
Stop Bits
The Stop Bits can be selected for 1 or 2. If 2 stop Bits are selected the Parity
will be set to none. The default is 1.
Parity
The parity may be selected to be None, Even or Odd. Even and Odd Parity can
be used only with 1 Stop Bit. The default is “None”.
Protocol
This is the protocol used over the Repeater Port. It can be set to Modbus RTU,
Modbus ASCII or Modbus Mixed. It does not determine what protocol is used
over TCP/IP. The messages will be converted if required. When set to Modbus

Mixed, the messages are sent as received with no RTU/ASCII conversion. The
default is Modbus RTU.
Initial Delay
This is the time in milliseconds that will be waited for a response before freeing
the repeater port for other connections. The default is 200 ms.
Char Delay
This is the time in milliseconds that will be waited between characters on the
Repeater Port before freeing it for other connections. The default is 20ms.
Security Parameters Menu

Selecting Configuration Option 4 displays the Security Parameters Submenu
changed.
This submenu allows parameter changes that determine who has access via the
network.
Passwords are case sensitive. When changing a password parameter, the
password can be cleared by entering ‘return’ at the Password: and Verify:
prompt.
Figure 7. Security Parameters Submenu of the OMNI Modbus Mux

Module.

Serial Password
If a password is entered here, it will be required when using the on-board serial
DB-9 connector configuration port. (It may be cleared by hitting return for the
password and later verification). If cleared no passwords will be required. The
default password is omni (lower case). The passwords are case sensitive. If you
have forgotten your password, contact OMNI Technical Support for the
procedure to recover it.
Telnet Password
This is the Password required when performing remote configuration of this
module using Telnet. The password can be cleared and if cleared, no password
will be required. The default password is omni (lower case). The passwords are
case sensitive. To disable Telnet access set the Telnet port to 0 (zero) instead of
the standard default of 23.
TCP/IP Password
This is a password required for any connection to the Modbus or Modbus/TCP
port numbers. An OMNI “Password Needed” exception code (5) will be
returned for any transaction until the password is written to data location 4850.
If cleared, no password will be required. The password is cleared by default.
Respond to Ping
Responses to ICMP Echo Requests or Pings can be enabled or disabled for
added security. The default value is Enabled.
IP Filter & Filter Mask

Connections to the Modbus and Modbus/TCP ports can be limited to an
individual IP address or a range of IP addresses. The mask determines which
bits are significant when testing the address. If the IP Filter is set to 0.0.0.0, it
will be disabled.
MAC Addresses
Media Access Control (MAC) addresses provide the highest level of security.
Connections can be limited to a list of hardware Ethernet addresses. This limits
access to a particular machine. If they are set to zeros they will be disabled. The
entry can be set to zero by entering a single zero otherwise enter the 12 hex
characters. With OMNI SE firmware v1.24 and above, you may enter the MAC
address with the corresponding dashes - for example: 00-90-C2-C0-2D-3F.

System Information Menu

Selecting Configuration Option 5 displays the System Information Submenu
(Figure 8). These items are displayed for information only. No changes are
possible.
MAC Address
The MAC address shown in
this figure is an example
only. The actual MAC
address is specific to each
module.
Figure 8. System Information Submenu of the OMNI Serial/Ethernet-

Modbus Mux (SE) Module.
MAC
The Media Access Control (MAC) is the hardware Ethernet address of the
Modbus Mux. It is specific to each board.
Con
Shows the IP address of all Encapsulated Modbus or Modbus/TCP connections
along with the TCP/IP port to which it is connected. The port number can be
used to tell if the connection is Encapsulated Modbus or Modbus/TCP.
Telnet
Shows the IP address of the user currently connected via Telnet.
Last Telnet
Shows the IP address of the last Telnet session.
Modicon Compatible
Shows if the Ethernet Host port is enabled for Modicon compatibility. This field
is display only. Modicon compatibility must be set in the OMNI configuration
from either OmniCom or the OMNI front panel.

Omni Firmware Ver

Shows the version of the OMNI firmware. This field is display only.
Advanced Parameters Menu

Selecting Configuration Option 6 displays the Advanced Parameters Submenu
changed.
This submenu allows parameter changes that determine how data is sent over the
network. Warning: Use Caution when changing these parameters!
Figure 9. Advanced Parameters Submenu of the OMNI Serial/Ethernet-

Modbus Mux (SE) Module
ReXmit Min
This field may be useful for VSAT communications. A time in milliseconds
that represents a lower boundary for a retransmit time out. The default is 10ms.
Note: Beware of reducing this, since modern hosts try to ack only every second
segment. If the time out is too small, the SE module will unnecessarily
retransmit if it doesn’t get the ack for the first of the two segments (especially on
a fast LAN, where the RTT measurement will tempt you to set a small time out).
ReXmit Max
This field may be useful for VSAT communications. A time in milliseconds
that represents an overall upper boundary for the retransmit time out. The
default is 10000 ms.
Nagle Algorithm

Nagle's algorithm is a means of improving the efficiency of TCP/IP networks by

reducing the number of packets that need to be sent over the network. The
default is Enabled.
Logging Parameters Menu

Selecting Configuration Option 8 displays the Logging Parameters Submenu
changed.
This submenu is used to enable System Logging which is the UDP transmission
of event notification messages across networks to event message collectors.
Examples of Syslog notification messages sent by the OMNI SE Module are
listed in Appendix B.
Figure 10. Logging Parameters Submenu of the OMNI Serial/Ethernet-Modbus

Mux (SE) Module
Syslog IP
The Logging page is used to enable the logging of system information and alerts
called the "Syslog". The syslog protocol provides a transport for the
transmission of event notification messages across networks to event message
collectors, or syslog servers, using UDP via port 514. The OMNI SE firmware
follows the syslog protocol outlined in RFC 3164. See Appendix B for a list of
example syslog messages. Note: It is recommended to use a static IP address
for the Syslog PC/Server instead of an address obtained using DHCP.
View System Log

Displays up to 250 Syslog event messages stored in RAM. These messages are
only stored if the Syslog is enabled and is cleared when the SE module is reset.

Debug Options Menu

Selecting Configuration Option 9 displays the Debug Options Submenu (Figure
11). Note: The Debug Option is not available with the Serial port connection.
Note 2: Debugging will degrade communications performance. Entering one of
the option letters will show different debug displays.
This submenu provides for a display of messages being received from and
transmitted to the OMNI SE and Host.
Figure 11. Debug Options Submenu of the OMNI Serial/Ethernet-Modbus

Mux (SE) Module
Debug All
Communication messages are displayed which represent Modbus messages
going to (>) and from (<) the Host (H) and the internal messages going to (>)
and from (<) the Ethernet Module (E) relative to the Host. See example in
Figure 12.

Figure 12. Debug All (9A) sample of the Debug Submenu

The first set of numbers represent the relative timings in milliseconds between
messages. For example: the time on the second message line is 69 so there were
69 ms between the completion of the execution of the messages on line 1 and
line 2.
The next number (1 - 4) is the connection number. (There are up to 4
simultaneous connections per SE Module at any time.)
The “<E” indicates messages going to the Ethernet from the outside world.
The “>H” indicates messages going to the OMNI from the Ethernet.
The “<H” indicates messages going from the OMNI to the Ethernet.
The “>E” indicates messages going from the Ethernet to the outside world.
Debug Host
coming into (>) and going from (<) the Host (H). The Host is the OMNI flow
computer CPU module.
Debug Ethernet
coming into (<) and going from (>) the Ethernet (E). The Ethernet is the OMNI
SE Module’s Ethernet port.
Debug Repeater
coming into (>) and going from (<) the Repeater Port (R). The Repeater is the
OMNI SE Module’s Repeater port.

Appendix A: Communicating Across Subnets

Appendix B: Example Syslog Messages

<181>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Ethernet card restart
<181>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Network up
<181>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Ethernet board reset - IP: 192.168.157.216
<181>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Ethernet board reset - Serial
<180>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Ethernet Flash download - IP: 192.168.157.216
<181>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Ethernet set to factory defaults - IP:

192.168.157.216
<181>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Ethernet set to factory defaults – Serial
<182>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Ethernet configuration change - IP:

192.168.157.216
<182>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Ethernet configuration change - Serial
<180>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Serial password changed - IP: 192.168.157.216
<180>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Serial password changed - Serial
<180>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Telnet password changed - IP:

192.168.157.216
<180>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Telnet password changed - Serial
<180>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: TCP password changed - IP: 192.168.157.216
<180>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: TCP password changed - Serial
<180>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Invalid Serial password attempts
<180>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Invalid Telnet password attempts - IP:

192.168.157.216
<180>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Invalid TCP password attempts - IP:

192.168.157.216 Port: 502
<181>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Lost password sequence entered - Serial
<182>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Ping request - IP: 192.168.157.216
<182>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Syslog enabled - IP: 192.168.157.216
<182>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Syslog enabled - Serial
<182>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Syslog disabled - IP: 192.168.157.216
<182>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Syslog disabled - Serial
<182>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Debug on - IP: 192.168.157.216
<182>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Debug off - IP: 192.168.157.216

<181>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: IP address change - IP: 192.168.157.14, New

IP: 192.168.157.17
<181>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: IP address change – Serial, New IP:

192.168.157.17
<182>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Port blocked - IP: 192.168.157.216 Port: 502
<182>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: IP filter rejection- IP: 192.168.157.216 Port:

502
<182>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: MAC filter rejection- IP: 192.168.157.216

Port: 502
<182>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Modbus timeout - IP: 192.168.157.216 Port:

502
<182>Jan 20 10:46:03 192.168.157.14 OmniSE[6C159D]: Modbus exception - IP: 192.168.157.216 Port:

502 Code: 05

Appendix C: Network Printing Error Codes
These codes are shown in the “value” column in the OMNI flow computer’s
Alarm report:
0 Error cleared
1 Printer socket open error or error establishing socket
2 Receive Job Command error
3 Receive Control File Command error
4 Control File error
5 Receive Data File Command error
6 Error while sending report
7 Error while sending nulls
8 Job Done Character error
255 Network parameter change (SE Module IP Address or Printer IP address
changed).

Appendix D: Setting a Temporary IP Address

for older versions of OMNI SE Firmware
For OMNI SE firmware v1.21 and below, you may set a temporary IP Address
using the following method. This method uses two utility programs (ARP and
PING) on a PC that is connected to the same network as the flow computer with
the SE module installed. This example uses the MAC address of 00-90-C2-C0-
2D-3F and sets a desired IP address of 200.100.101.13. The MAC address you
use will be the one from your module and the IP will be what you have selected
for your network.
All computers use a table to map IP addresses to hardware addresses for the
network. The values in the table are filled in using an “Address Resolution
Protocol”. The table is referred to as the ARP table. This method sets an entry in
the ARP table and then uses ping to propagate this entry to the SE module.
MAC and IP Addresses  Type cmd from MS Windows desktop Start/Run menu or bring up a DOS
The MAC address and IP box on the PC.
 Ping the address you intend to use to be sure it is not in use by another
address used here are for
example purposes only.
You must use the MAC
address from your SE device by typing: ping 200.100.101.13 (substitute your desired IP address)
Module and the IP address you should receive time outs for the pings. If you receive any replies then
you have selected for your that address is in use and another one should be chosen.
network.
A problem may be encountered when replacing an SE module with a new
MAC Address for Unix module already set to the same IP address or when attempting to set the
Systems
new module to the same IP address that was previously in use.
The example shown is for
Microsoft Windows. On a The ARP table in the PCs, routers, switches and other network devices may
Unix system, the MAC
address is typed as already contain a mapping of the IP address to the previous hardware MAC
00:90:C2:C0:2D:3F. ID. All TCP traffic for that IP address will be directed to the hardware
MAC ID of the previous board and will not be seen by the new module.
The solution is to ensure that the IP address is cleared out of the ARP
tables. To do so, bring up a DOS session and type: arp –d IP address in
use. Example: If the IP address is 200.100.101.13 then the command line
would be: arp –d 200.100.101.13
 Type: arp –s 200.100.101.13 00-90-C2-C0-2D-3F. This sets up the ARP
table on the computer and associates the IP address with the hardware
address of the SE module.
 Type arp –a to verify the entry was accepted.
 Type: ping 200.100.101.13 . The first attempt will produce a time out while
the SE module reconfigures its address. The subsequent attempts should
receive a reply.
If the ping is unsuccessful, especially where routers or switches are
involved, allow sufficient time for the new IP address and MAC ID to be

propagated into the ARP tables of the various routers and switches on the
network and then attempt to ping the IP address again.
 Use Telnet to access the configuration menus by typing: telnet
200.100.101.13. Set the IP address, Netmask, and Default Gateway. Save
the parameters. Any other parameters may be changed and saved at this
time.
 Remove the entry in the ARP table by typing: arp –d 200.100.101.13.
Once you start getting replies from the ping, the IP address has been accepted by
the SE Module. This IP address is temporary and the SE module will revert to its
previous IP address after 5 minutes unless the IP address is changed and saved
while in a telnet session.
Note: The example shown is for Microsoft Windows. On a Unix system the
MAC address is typed as 00:90:C2:C0:2D:3F.

Serial/IP Software
Version 2.3.1
Appendix E: Using OmniCom for DOS over
OMNI discovered a problem TCP/IP
in Serial/IP Version 2.3.1,
which was corrected by OmniCom for DOS does not support TCP/IP directly but it can be used with
Tactical Software. An
“Serial Port Redirector” software to communicate with the Modbus Mux. The
redirector will “capture” serial port communications and route them over TCP/IP
updated version is available
on the Tactical Software
Web site. You must to a defined IP address and TCP port. (Note: OmniCom for Windows fully
download and install
Version 2.4 or above. supports TCP/IP directly and does not require this redirector.)
The suggested software to use is Serial/IP from Tactical Software. The software
may be downloaded for trial and purchased at www.tacticalsoftware.com.
Windows NT/2000
Under Windows NT and Windows 2000, any version of OmniCom for DOS is
compatible with Serial/IP. OmniCom is selectable for serial ports 1-4. Use
Serial /IP to redirect a serial port in that range, configure with the IP address and
TCP Port assigned to the Modbus Mux and set for “Raw TCP Connection”.
Windows 95/98
Under Windows 95 or 98, Serial/IP can only redirect communications when the
serial port is opened with an INT/14 driver. This requires a revision XX.73.15 or
above OmniCom for DOS. The latest version can be downloaded from
www.omniflow.com. To activate the INT 14 driver, select "TCP/IP 98" for
"Comm Media" on the OmniCom "Start Comm" menu.

SE Firmware Revision History

v1.53 The Ethernet would sometimes misinterpret the reponse from
the Repeater and log it as a Modbus exception to the Syslog -
problem was introduced in v1.50.
If the Syslog was enabled and the 2nd printer IP Address was
changed, the IP address logged in the Syslog for the Omni
became the changed Printer IP - problem was introduced in
v1.50.
v1.52 The Ethernet was not processing the reponse from the
Repeater port correctly - problem was introduced in v1.50.
v1.51 The TCP Password entry was never accepted when the port
was configured as Modicon compatible.
The Ethernet was not communicating with the Omni if the
Ethernet cable was not connected on power up. Once the
cable was connected, the Ethernet would continue but
features such as Network Printing and Ethernet configuration
via OmniCom would not be enabled.
v1.50 Systems Menu – added the OMNI flow computer firmware
version display.
Network Printing was added allowing for two network
printers per SE Module (in addition to the existing local RS-
232 printer supported by the flow computer). See Appendix
C for Network Printing error codes.. Note: The flow computer
firmware must be a version that supports network printing.
SE Module configuration exchange with OMNI flow
computer allows configuration via OmniCom v1.25 and up
(SE Module firmware v1.50 and up). Note: The flow
computer firmware must be a version that supports
configuration of the Ethernet.
The IP Address, Netmask, Gateway, Host Modbus ID, and
Modicon Compatibility is now synchronized between the SE
Module and the OMNI flow computer. If the IP address sent
to the SE Module from the OMNI is zeros, the SE Module
sends its IP address, Netmask, and Gateway to the OMNI (SE
Module firmware v1.50 and up).
If the downloader fails during a firmware upgrade due to not
enough extended memory it will free the memory used for
both the Syslog and for Network Printing.

v1.26 Security Menu - 4 more MAC address filters were added for a
total of 8.
Ethernet Menu - the Ethernet ID is now used to store
information when configuration is set to defaults:
1) If the user has restored the configuration to factory
defaults, the Ethernet ID is set to "FD111222333444" where
the numbers represent the configured IP address (in decimal
notation without the dots) before the reset occurred.
2) On startup, after the configuration has been read from
FLASH memory, if the CRC check fails and has to be set to
defaults (this may happen when a user downloads an older
version of SE firmware than what is currently in the SE
Module) the Ethernet ID is set to "CRC111222333444".
3) If there is an error reading the FLASH memory for the
configuration block, the Ethernet ID is set to
"-XR111222333444" where "-X" is the error code returned
from the read:
"-1" = invalid address or range
"-2" = no valid ID block found
4) If there is an error writing to the FLASH memory for the
configuration block, the Ethernet ID is set to
"-XW111222333444" where "-X" is the error code returned
from the write:
"-1" = invalid address or range
"-2" = no valid ID block found
"-3" = flash writing error
5) The configuration is verified after a save. If the read fails
on the save, the Ethernet ID is set to "SVR111222333444".
If the CRC check fails on the save, the Ethernet ID is set to
"SVC111222333444" using the IP in the system parameters.
If the IP address does not verify, the Ethernet ID is set to
"SVI111222333444" using the IP in the system parameters.
6) If the IP Address is all zeros on startup, the 4th byte of the
Ethernet ID is set to 'Z'.
Debug Menu - Changed the order of the debug menu to (A)

Debug All, (B) Debug Host, (C) Debug Ethernet and (D)
Debug Repeater.
Modbus communications - support for broadcast messages

was added.
Re-added the 5 second time delay after restart to allow the

Omni to initialize.
If an IP Address of all zeros is sent to the SE Module from

Telnet or onboard DB9 serial port configuration, it will not be
saved in the configuration.

If the IP Address is all zeros on start up, the address is set to

the default of "10.0.0.1" .
After three invalid password attempts in Telnet configuration,

a one minute lockout is imposed.
When configuring the Omni from the onboard DB9 serial
port and using the backspace key, data was not displayed
properly on the input line.
v1.25 Ethernet Menu - Allow escape key when entering the
Ethernet ID. Changed the text from "Modbus Port" to
"Encap. Modbus Port".
Security Menu - Allow escape key when entering MAC
addresses.
Debug Menu - Added "Debug Ethernet" and "Debug
Repeater" selections.
All menus - Backspace displayed garbage on the screen.
Added the ability to obtain and reset the Telnet Port via UDP
before a Configuration session (available with Network
Utility v1.07 and up).
Added an "Inactivity" message when in the Debug mode if
the Modbus communication's socket is closed due to Modbus
inactivity time out.
The 5-minute Telnet time out timer is refreshed every time a
debug message is printed during Modbus communications.
This change allows continuous debug data to be captured
without timing out. After 5 minutes of Modbus inactivity, the
Telnet session will time out.
Preset Single Register (function code 06) was not properly
handling 32-bit long integers and floats writes and resulted in
a short message sent to the flow computer and thus incorrect
values written.
Added a refresh of the configured Netmask and Gateway
when the IP address is changed.
Removed the setting of the Netmask based on class when the
IP address was changed via the "Set IP Address" feature in
Network Utility.
Removed the ping of the IP address configured in the SE
module in order to update ARP tables on network devices
when replacing an SE module using the same IP address as
the previous SE module. It now pings the configured
Gateway IP address instead of the local IP address.

The ARP table entries for the Ethernet devices on the local
subnet are already updated automatically when a new session
is initiated with the SE module.
Removed the 5 second time delay at start up before being
able to establish communications after power up or Board
Reset and now it just waits for the sockets to initialize before
communications is allowed.
enough extended memory it will free the memory used for the
Syslog.
v1.24 Ethernet Menu - Added a 15 character "Eth ID". The ID can
be used to name or describe the Ethernet Module. Removed
the "Set IP via Ping" flag.
Host Menu - Baud Rate - 57600 was removed from the Host
choices.
Remote Menu - Baud Rate - 57600 was listed as a choice but
when selected gave an "Invalid Parameter" message. 57600
was enabled as a valid selection.
Security Menu - Added a "Respond to Ping" flag. The
choices are (0)Disabled (1)Enabled. The default is Enabled.
Allow MAC addresses to be entered with corresponding
hyphens between numbers.
System Info Menu - Modicon compatibility is auto-detected
on start up and the status is displayed as Enabled or Disabled.
Logging Menu - Added the System Logging menu and
functionality (Syslog).
Added an ICMP Handler to handle pings.
The IP Address can no longer be configured using the "arp -
s" command.
Added a 5 second time delay after restart to allow the Omni
to initialize.
If the physical connection to the OMNI was broken, the
connections were remaining open. Now all connections are
closed when the physical link is detected broken. When the
link is re-established, it is logged to the System Log (if
enabled).
SE Module responded to a ping if the MAC address matched
but was not checking that the IP address matched as well.

The check for the TCP password is now skipped on messages

going through the repeater port.
Connections via the serial port at the same time as a Telnet
connection was causing the configuration menu display to
lock up and time out at the PC side.
Configuration menu display was stopping before end of menu
when using Telnet.
Debug All not keeping up on long (255 bytes) messages.
Display a message to the user if Debug mode is selected
when on a serial connection.
v1.23 Added ‘Advanced’ and ‘Debug’ entries to the menu. Added
new parameters in the Advanced menu to help with TCP/IP
over VSAT. Minimum and Maximum retry on packets
retransmission as well as the ability to turn the Nagle
Algorithm on or off was added. Debug was placed on menu
instead of typing 'X' or 'Z'.
v1.22 Removed ICMP handler - use library instead. IP change via ping
is permanent.
v1.21 Added disable of ICMP (Ping) and further checks in the ICMP
handler.
v1.20 Changed tasks to speed up. Added debug through Telnet with 'X'
and 'Z'. Added Flash download support.
v1.10 Corrected a problem with Modbus/TCP queued requests getting
ignored.
v1.09 Added keepalive to detect dropped connections when the
inactivity time out is set to zero. Added a ‘Reset’ on the serial
and telnet menus to reset the ethernet board via telnet.
v1.08 Added ICMP Handler and fixed the handling of unknown
Modbus function codes so they fall through untouched. Added
tcp_tick in handlers to detect if a socket is closed in the middle of
a transaction. Added ‘exit’ on the serial and telnet menus.
v1.07 Removed Modbus Delay parameter. Added the ability to set a
Temporary IP address using arp and ping on a PC so serial
connection is not required. Change the default Subnet Mask to
Class A 255.0.0.0.
v1.06 Fixed bug when changing TCP Port where it didn't take effect
until reset.
v1.05 Added ping to clear up arp tables.
v1.04 Padded connection buffers.

v1.03 Minor Menu Changes.

v1.02 Enabled the gateway parameter.
v1.01 Initial Version

Last Updated: 08 31 2004 TB # 000314B
Communicating with Auto-Adjust Turbo-Meter

Gas Flowmeters
Contents
information contained in the AAT 1200 Flowmeter Theory of Operation ...................................................... 2
Revision 23.73/27.73+. Omni Flow Computer Logic............................................................................... 2
Wiring Auto-Adjust® (AAT) Turbine Flowmeter (Slot Sensor) signals
to E Type Combo Modules (Omni 6000 and 3000)……………………………..4
Omni Technical support is Wiring Auto-Adjust® (AAT) Turbine Flowmeter (Slot Sensor) signals
available at:
Phone: (281) 240-6161
to E Type Combo Modules (Omni 6000 and 3000)………………………...…...5
Fax: (281) 240-6162 Flow Computer Configuration…..……………….....……………………………...6
Technical information is Miscellaneous Configuration Meter Run Settings.......................................................... 6
available on our website at: Meter Run Setup Entries ............................................................................................... 6
www.omniflow.com
or send email to:
Flow Computer Database Addresses and Index Numbers ............................ 8
Scope
This technical bulletin applies to firmware revisions 23.73+ and 27.73+ of Omni
6000/Omni 3000 flow computers, for gas flow metering systems.
Abstract
The Auto-Adjust (AAT) Turbo-Meter generates a self-checking output that is
derived from the ratio between the main and sensing rotor pulses. This output is
referred to as Delta A. The self-checking feature indicates how much
adjustment the meter is making, thereby warning the user of meter or flow-
conditioning problems. The Omni flow computer totalizes the flowmeter pulse
input signal received from the Auto-Adjust Turbo-Meter.
TB-000314B 23/27.73+ 1
AAT Flowmeter Theory of Operation

The Auto-Adjust (AAT) Turbo-Meter was introduced in the early 1980's. This
meter has larger bearings, rugged rotor shafts, and unique dual rotor, is similar
to that for a single rotor turbine. However, the second rotor, or sensing rotor, is
unique in that its speed reacts to changes that occur to the main rotor. The
pulse signals from the two rotors are fed into the flow computer where
algorithms calculate an adjusted volume and a self-checking value called "Delta-
A". The adjusted volume is based on original factory calibration accuracy and
gives the ATT the ability to compensate for a number of conditions that could
degrade the accuracy of a single rotor turbine meter. While the meter is
operating, the Delta-A output detects shifts in accuracy that could go unnoticed
in a single rotor turbine meter. The periodic Delta-A reading indicates that a
shift in accuracy did occur.
Gross Flow Rate Equation
Omni Flow Computer Logic

Qv=(Pm/Km)-(Ps/Ks) *3600
Adjusted Volume
Equation - The Omni flow computer determines the actual flow rate from the live pulse
(Pm/Km) - (Ps/Ks) * Time frequency signal inputs, which has been assigned and configured. This
calculation is done every 500 milliseconds using pulses read from the Main and
Pm: Main Rotor Pulses Sensing rotors of an Auto-Adjust Turbo-Meter. By combining these pulses
Ps: Sensing Rotor Pulses along with the unique pulse factors for each rotor in an adjusted volume
Km: Main Rotor Pulse (Cumulative Gross) equation, a gas measurement volume will be calculated. In
Factor addition to the adjusted volume equation, algorithms are included that provide
Ks: Sensing Rotor Pulse corrections to the volume totalization for conditions of Leakage flow, Resonant
Factor No-Net flow, Severe flow pulsation or Non-Steady flow.
Self-Checking (Delta-A) Calculation  This calculation is performed after
25,000 main rotor counts are accumulated or after a time interval of 512
seconds has elapsed, whichever occurs first. The equation for this
calculation compares the speed ratio of the Main rotor and Sensing rotor with
the average speed ratio determined at factory calibration. The average
factory value is represented by the "A-bar" value in percent. The calculation
difference in field operation from the A-bar value is the % Deviation or Delta-
A reading.
Warning Flags and Alarm Outputs  The logic and algorithms in this
section compare error conditions and Delta-A values to limits that are fixed or
operator selected. Warning flags, alarms, and messages are set depending
upon which limits are exceeded.
Un-Adjusted Volume Calculation  This section shows how the
"mechanical" or Un-Adjusted volume is properly calculated using the pulses
from the Main rotor only. This volume is to be used in the measurement
totalization when pulses from the Sensing rotor are unavailable or when the
gas flow rate is below the minimum for the Adjusted output.
Volume Totalizer Increment  This section shows how the totalizer
registers for both Adjusted and Un-Adjusted volumes are incremented after
the calculation are performed each second.
2 TB-000314B 23/27.73+
TB-000314B Communicating with Auto-Adjust Turbo-Meter
AAT Flow Chart
Figure 1. Flow computer logic flow diagram for the AAT gas flowmeter.
TB-000314B 23/27.73+ 3
4 TB-000314B 23/27.73+
TB-000314B 23/27.73+ 5
Flow Computer Configuration

The flow computer configuration settings that are specific to the AAT flowmeter
are entered in the miscellaneous configuration meter run menu and the meter
run setup menu. You must enter the miscellaneous configuration meter run
settings first and then proceed to the meter run setup entries. These
configuration settings at this time can be entered via the Omni flow computer’s
front panel keypad.

The following miscellaneous configuration meter run settings are required for
each AAT gas flowmeter:
Select Flowmeter Device Type  Enter [7] for each meter run that you want
to select the AAT gas flowmeter as the device type.
Flow I/O Point  Flowmeter pulse signals can only be assigned to the 3rd and
4th input channels of the E combo modules. Assign the Main Rotor pulse to the
Omni channel number that corresponds to the 3rd input channel on an E-Combo
module and the flow computer program will assume the Sensing Rotor Pulse
signal is wired to the 4th input channel of the same E-Combo module.

The following meter run setup entries are required for each AAT gas flowmeter:
M.R. Factor  The Main Rotor (MR) Factor value (Pulses/MCF or /M3) of an
individual Auto-Adjust Turbine meter can be found on the METER FACTOR
badge or on the factory calibration documents.
S.R. Factor  The Sensing Rotor (SR) Factor value (Pulses/MCF or /M3) of an
individual Auto-Adjust Turbine meter can be found on the METER FACTOR
badge or on the factory calibration documents.
M.O. Factor  The Mechanical Output (MO) Factor value (Pulses/MCF or /M3)
of an individual Auto-Adjust Turbine meter can be found on the factory calibration
curve for the meter. This value is determined mathematically from the mechanical
output of the meter, change gears, internal gearing, and blades on the pulsar
wheel.
A_Bar %  The Average Relative Adjustment (A) value (%) of an individual
Auto-Adjust Turbine meter can be found on the METER FACTOR badge or on the
factory calibration documents. The purpose of the Adjusted volume calculation is
to provide a measurement registration that is adjusted back to original factory
calibration accuracy, compensating for meter changes or for abnormal flow
conditions. These field or operating Delta_A values can be compared with those
at factory calibration.
BTSF  Blade Tip Sensor Factor (BTSF) for meter
AlarmBand H %  Alarm band high limits %. The logic and algorithms in
this section compare error conditions and Delta-A values to limits that are fixed or
Operator selected. Delta_A above normal limits.
AlarmBand L %  Alarm band low limits %. The logic and algorithms in this
Operator selected. Delta_A below normal limits.
Warning Hi %  Alarm band high limits %. The logic and algorithms in this
Operator selected. Delta_A above normal operating limits.
Warning Lo%  Alarm band low limits %. The logic and algorithms in this
Operator selected. Delta_A below normal operating limits.
6 TB-000314B 23/27.73+
AutoAdj Set (Set1)  The adjusted volume calculation is done every 500mS
cycle using pulses read from the Main and Sensing rotors of an Auto-Adjust
Turbo-Meter. In addition to the adjusted volume equation, algorithms are included
that provide corrections to the volume totalization for condition of Leakage flow,
Resonant No-Net flow, Severe flow pulsation or Non-Steady flow.
Set1 = 0 ; Enable the auto adjust volume calculation, self-checking , flags and
alarms.
Set1 = 1 ; Enable the auto adjust volume calculation, self-checking , disable
flags and disable alarms.
Set1 = 2 ; Enable the auto adjust volume calculation, disable self-checking ,
disable flags and disable alarms.
Set1 = 3 ; Disable the auto adjust volume calculation, disable self-checking ,
disable flags and disable alarms.
Un-Adj Set (Set2)  This section shows how the "Mechanical" or Un-Adjusted
volume is properly calculated using the pulses from the Main rotor only. This
volume is to be used in the measurement totalization when pulses from the
Sensing rotor are unavailable or when the gas flow rate is below the minimum for
the Adjusted output.
Set2 = 0 ; Enable the UN-Adjusted volume calculation.
Set2 = 1 ; Disable the UN-Adjusted volume calculation
Meter Run Data

To configure meter run setup on the flow computer LCD display, press [Prog]
[Meter] [n] [Enter] on the Omni front panel keypad (where “n” equals the meter
run number, 1 to 4, you want to setup) when in the setup Mode. The following
entries will display:
METER RUN #1
Meter ID
Select Product No.
GC Stream #
Flow Low
Flow High
G FullScal
M FullScal
Active Freq.
M.R.Factor
S.R.Factor
M.O.Factor
A_bar%
BTSF
AlarmBand H%
Alarm Band L%
Warning Hi %
Warning Lo %
AutoAdj Set
Un-Adj Set
Meter Factor
Meter Model
Meter Size
Serial No.
Select Trans Dens?
TB-000314B 23/27.73+ 7
Warning and Alarm Messages

The following warning or alarm messages will be displayed when the alarm
condition occurs:
AAT ABN Warning
AAT ABN Alarm
Non-steady Flow Alarm
Non-steady Flow Warning
No Flow or No Pulses
(Both)
Leakage/Resonant No-Net
Flow
No Main Rotor Pulses
No Sensing Rotor Pulses
Flow Computer Database Addresses and

Index Numbers
The following tables list the Modbus database addresses within the Omni
assigned to the Auto-Adjust Turbo metering feature. These tables are
categorized per data type.
Meter Run Alarm & Status Points  Real Time Data

1 2 3 4 1 2 3 4
AAT ABN Warning 2178 2278 2378 2478 System Status Word 3158 3258 3358 3458
AAT ABN Alarm 2179 2279 2379 2479 Non-Steady Flow Status 3159 3259 3359 3459
Non-steady Flow Alarm 2180 2280 2380 2480 Auto Adj. Abnormal Status 3160 3260 3360 3460
Non-steady Flow Warning 2181 2281 2381 2481 Auto Adjust Alarm Status 3161 3261 3361 3461
No Flow or No Pulses (Both) 2182 2282 2382 2482 Warning/alarm message #1 4123 4223 4323 4423
Leakage/Resonant No-Net Flow 2183 2283 2383 2483 Warning/alarm message #2 4124 4224 4324 4424
No Main Rotor Pulses 2184 2284 2384 2484 Warning/alarm message #3 4125 4225 4325 4425
No Sensing Rotor Pulses 2185 2285 2385 2485
Meter Configuration & Setup Entry Data

1 2 3 4 1 2 3 4
M.R. Factor 17501 17601 17701 17801 Auto Adjust Set (Set 1) 3156 3256 3356 3456
S.R. Factor 17502 17602 17702 17802 Un-Adjusted Set (Set 1) 3157 3257 3357 3457
M.O. Factor 17503 17603 17703 17803
A_Bar % 17504 17604 17704 17804
Blade Tip Sensor (BTSF) 17505 17605 17705 17805
Alarm Band High Limit % 17506 17606 17706 17806
Alarm Band Low Limit % 17507 17607 17707 17807
Warning Band High Limit % 17508 17608 17708 17808
Warning Band Low Limit % 17509 17609 17709 17809
8 TB-000314B 23/27.73+
TB-000314 Communicating with Auto-Adjust Turbo-Meter
32-Bit Integer Data

1 2 3 4 1 2 3 4
Sensing Rotor Pulses (Batch) 5196 5296 5396 5496
Sensing Rotor Pulses (Daily) 5197 5297 5397 5497
Cumulative Un-Adjusted Total 5198 5298 5398 5498
32-bit IEEE Floating Point Data

1 2 3 4 1 2 3 4
Previous Hour Average – Delta A 8528 8628 8728 8828
Previous Day Average – Delta A 8546 8646 8746 8846
Calculated Delta A 8569 8669 8769 8869
TB-000314B 23/27.73+ 9
Date: 26 Feb ‘07 Author(s): IP Version: TB-010701B

Date: 30 Jan ‘02 Author(s): KDE and IP Version: TB-010701
C
Coom
mmmuunniic
caattiin
nggw wiitth
hK Koon
nggs
sbbe
errg
gMMe erriin
ette ngg
M
MPPU
U1 1220000U Ullttrra
assoon
niic
cG Ga
assFFllo
owwm
meette
errss
Contents
User Manual Reference Scope....................................................................................................... 1
This technical bulletin Abstract ................................................................................................... 2
supplements the information
MPU 1200 Ultrasonic Flowmeter Theory of Operation....................... 2
Manual, applicable to OMNI Flow Computer Logic .................................................................. 2
Revision 23.73/27.73+.
Wiring Installation .................................................................................. 4
Communicating with OMNI Combo Module Terminal Assignments................................................. 5
Kongsberg Metering MPU 1200 Terminal Assignments.................................................................... 6
MPU 1200 Ultrasonic Forward & Reverse Flow Signals ..................................................................... 7
Gas Flowmeters
Forward Flow Only with (Dual) Pulse Fidelity & Integrity Checking ............. 8
The Kongsberg Metering
MPU 1200 ultrasonic
Forward & Reverse Flow with (Dual) Pulse Fidelity & Integrity Checking .... 9
flowmeter measures gas MPU 1200 Configuration ...................................................................... 10
flow by using an
upstream/downstream Miscellaneous Configuration Settings ............................................................ 10
transit time method of Serial Port Settings.......................................................................................... 10
acoustic pulses. This
device communicates with OMNI 3000/6000 Configuration............................................................ 10
OMNI flow computers via Miscellaneous Meter Run Configuration Settings .......................................... 10
OMNI’s ‘SV’ process I/O
combo module using a Meter Run Setup Entries ................................................................................. 11
proprietary Modbus
protocol. To use the scaled
OMNI 3000/6000 Database Addresses & Index Numbers ................. 12
pulse output of the OMNI 3000/6000 User Displays ........................................................... 15
Kongsberg Metering, the
flow computer must have Meter Run Data............................................................................................... 15
either an ‘A’, ‘B’, or ‘E’ SV Module Serial Port .................................................................................... 16
combo module installed.

available at:
Scope
Phone: (281) 240-6161 This technical bulletin applies to firmware revisions 23.73+ and 27.73+ of
Fax: (281) 240-6162 OMNI 3000/6000 flow computers for gas flow metering systems.
Technical information is
available on our website at:
www.omniflow.com
Or send email to:
TB-010701B 23/27.73+ 1
Abstract
Ultrasonic gas flowmeters determine the linear gas velocity through the meter
tube by using multiple acoustic pulse reflection paths. These meters analyze the
acoustic paths employing an upstream/downstream transit time measurement
method. The OMNI flow computer totalizes either the flowmeter pulse input
signal or the actual uncorrected volume data received from the MPU 1200.
MPU 1200 Ultrasonic Flowmeter

Theory of Operation
Kongsberg's ultrasonic gas flow-metering technology incorporates multiple pairs
of transducers into a smart digital inferential instrumentation device. This
device is installed into a gas pipeline system to measure gas flow. Each pair of
transducers emits ultrasonic (acoustic) pulses that travel bi-directionally, to and
from each transducer in the pair.
The MPU 1200 has six pairs of transducers positioned across it so that the path
between each transducer has an axial component; i.e., one transducer is
upstream relative to the other. When the downstream transducer emits an
ultrasonic pulse that is slowed down by the velocity of the fluid, the pulse takes
longer to travel to the upstream transducer than with no flow. When the
upstream transducer emits a pulse that is aided by the velocity of the fluid, the
pulse takes less time to travel to the downstream transducer. Ultrasonic
flowmeters that apply transit time methodology, such as the MPU 1200,
measure these two transit times to determine both the velocity and the speed of
sound of the fluid. The flowmeter can measure gas velocity for bi-directional
(forward/reverse) fluid flow.

The OMNI flow computer can determine the actual flow rate from data received
either serially from the MPU 1200 flowmeter or from a live pulse frequency
signal input if it has been connected, assigned, and configured. In this
application, Modbus serial communication is the primary measurement source.
The pulse frequency signal serves as a backup flow measurement, should the
Modbus serial communication link fail or be disconnected.
The MPU 1200 serially transmits the accumulated volume to the OMNI. The
flow computer obtains a calculated volume increment by subtracting the new
accumulated volume from the last accumulated volume it received. The MPU
1200 flowmeter updates its totalizers on a regular interval depending upon
flowing conditions and configuration settings. Updating the OMNI totalizers on
this same interval would result in somewhat erratic totalizers and sampler pulse
outputs, which could upset other equipment connected to the flow computer.
The OMNI therefore provides a smooth totalizer update by monitoring the time
interval between MPU 1200 totalizer updates, and distributing the volume
increment over a matching time interval.
2 TB-010701B 23/27.73+
TB-010701B Communicating with Kongsberg Metering MPU 1200 Ultrasonic Flowmeters
Start
Are
MPU No Set MPU
Communications Communication
OK Failed Alarm
?
Yes
Is
Clear MPU Yes
Pulse I/O Clear Pulse Signal
Communication
Assigned Suspect Alarm
Failed Alarm
?
No
Is
Transmitter No Totalize Flow Based on
Flowrate in Correct Disable Totalizing
Pulse Input Signal
Direction
?
Yes
Set Meter Run

Is Not Active
Pulse I/O No Clear Pulse Signal
Assigned Suspect Alarm
?
Yes
Calculate Flowrate
Based on Pulses
Compare Flowrate
Based on Pulses to
Serial Data Flowrate
Is
Flowrate No Set Pulse Signal
Based on Pulses
Suspect Alarm
within Limits
?
Yes
Clear Pulse Signal

Suspect Alarm
Totalize Flow Based on

Transmitted Serial Data
End
Figure 1. Flow computer logic flow diagram for the MPU 1200
ultrasonic gas flowmeter.
TB-010701B 23/27.73+ 3
If there is a communication failure between the two devices, the OMNI will not
receive serial data. However, the MPU 1200 may be fully operational and
continue to accumulate volume. In this case, if a pulse signal is available from
the MPU 1200, the OMNI flow computer will automatically continue to
accumulate flow based on this flow pulse train. When normal communications
resume, the flow computer will validate and adjust its internal totalizers if
necessary to match the volume indicated by MPU 1200 internal totalizer. The
flow computer automatically adjusts its totalizers to account for the small
amount of flow that takes place before it detects that a communication failure
has occurred (i.e., when the serial link fails, the OMNI does not immediately
start totalizing using the MPU 1200 pulse train because it takes several seconds
to determine if a failure has occurred).
If a pulse signal from the MPU 1200 is not available and the communication
link fails, the flow computer immediately stops totalizing. Once communication
is reestablished, the OMNI will adjust its internal totalizers to include volume
flow indicated by the MPU 1200 totalizer. In this case, the OMNI may have to
add a significant amount of flow to its totalizers depending upon how much time
the communication link was inoperative.
In some instances, adjusting the flow computer’s totalizers may not be desirable;
e.g.: if a flowmeter has been disconnected for a long period of time, or the MPU
1200 electronics package has been replaced. For these cases, there are flow
computer configuration settings that specify the maximum time that an MPU
1200 serial communication failure can exist and still be compensated by
adjusting the flow computer totalizers (default maximum time is 15 minutes).
Wiring Installation
Setting Up and Wiring There are several options for wiring an MPU 1200 ultrasonic meter to an OMNI
to OMNI Combo flow computer. The option to implement depends upon requirements of the
Modules flow metering system.
In order to communicate
with MPU 1200 ultrasonic Connect these devices via the 2-wire RS-485 serial interface from the MPU
flowmeters, the OMNI flow 1200 to an OMNI SV combo module serial port. This connection uses the
computer must be equipped
with at least one SV combo Modbus protocol to transmit the volumetric flow data that the MPU 1200
module (Model 68-6203). accumulates to the OMNI.
For instructions on jumper
settings and other process In addition to serial data, the OMNI can also receive live forward and/or reverse
I/O combination module flow pulse signals from the MPU 1200. The MPU 1200 transmits pulse
refer to Volume 1, Chapter frequencies through wires typically connected to an OMNI E combo module.
2 of the OMNI User Manual. Connecting two MPU 1200 pulse output channels to the OMNI can provide
pulse fidelity and integrity checking. To perform pulse fidelity checking, the
Serial Data OMNI must have one E combo module for each flowmeter and flow direction
Communications (forward/ reverse) requiring totalizing.
The serial interface between
these devices is 2-wire RS-
modified Modbus protocol.
4 TB-010701B 23/27.73+
OMNI Combo Module Terminal Assignments

Depending upon the implemented wiring option, the OMNI requires SV, E,
and/or A combo modules. The tables below specify the terminal assignments
for each module type. This information is necessary when connecting wires to
the OMNI. The terminal block number (TBn) on the OMNI back panel for each
combo module corresponds to the slot on the motherboard into which the
module is plugged.
OMNI SV Combo Module Back Panel Terminal Assignments (TBn)

Terminal Signal Description
1 Port # 1 (3): RS-485 B Wire
2 Port # 1 (3): RS-485 A Wire
3 Port # 2 (4): RS-485 B Wire
4 Port # 2 (4): RS-485 A Wire
5 Signal Return for 4-20mA Analog Outputs
7 Analog Output # 5: 4-20mA
Note: Numbers in parenthesis “( )” refer to SV module 2.
OMNI E Combo Module Back Panel Terminal Assignments (TBn)

1 Input Channel # 1: 1-5v, 4-20mA, RTD
2 Input Channel # 1: Isolated Signal Return
5 Input Channel # 3: Flowmeter Pulses
7 Double Chronometry Detector Switch Input (Active Low)
8 RTD Excitation Current Source Output #2
Signal Return for Terminals 5, 6, 7, 8, 9, 11 & 12 (Internally
10
connected to DC power return
TB-010701B 23/27.73+ 5
OMNI A Combo Module Back Panel Terminal Assignments (TBn)

Signal Return for Terminals 9, 11 & 12 (Internally connected to DC
10
power return
Analog Output # 2: 4-20mA or RTD Excitation Current Source
12
Output #2 (See JP12 Setting)
MPU 1200 Terminal Assignments

Use the X8 and X5 terminal blocks in the MPU 1200 to connect to the OMNI.
The tables below specify the terminal assignments for each of these terminal
blocks. This information is necessary when connecting wires to the MPU 1200.
MPU 1200 Terminal Block X8 Assignments

1 Output Channel #1A: Frwrd Flow Pulses – Open Collector (NPN)
2 Output Channel #1A: Frwrd Flow Pulses – Return
3 Output Channel #1B: Frwrd Flow Pulses – Open Collector (NPN)
4 Output Channel #1B: Frwrd Flow Pulses – Return
5 Output Channel #2A: Rvrse Flow Pulses – Open Collector (NPN)
6 Output Channel #2A: Rvrse Flow Pulses – Return
7 Output Channel #2B: Rvrse Flow Pulses – Open Collector (NPN)
8 Output Channel #2B: Rvrse Flow Pulses – Return
9 Flow Direction +
10 Flow Direction -
11 Measurement Valid +
12 Measurement Valid -
MPU 1200 Terminal Block X5 Assignments

23 Transmit/Receive Data (TxD/RxD–)
24 Termination (Negative)
25 Transmit/Receive Data (TxD/RxD+)
26 Termination (Positive)
27 Signal Ground
6 TB-010701B 23/27.73+
Forward & Reverse Flow Signals

Figure 2 shows a typical wiring installation between the MPU 1200 and an
OMNI 6000 of serial data and both forward and reverse flow signals. In this
example, assume that the OMNI has an A module plugged into slot TB5 and an
SV module in slot TB6.
KONGSBERG MPU 1200 OMNI FLOW COMPUTER

ULTRASONIC FLOWMETER BACK PANEL TERMINAL BLOCKS
Terminal Block A Combo Module Power Terminals

X8 Terminals (TB5) (TB11)
1 1 + + + + - - - -
Pulse Out 1A+
2 2
Pulse Out 1A-
3 3
4 4
5 5
Pulse Out 2A+ Pulse In 3 2.2K to 10K
6 6
Pulse Out 2A- Return 3 Ohm
7 7
Pulse In 4
8 8
Return 4
9 9
10 10
11 11
12 12
Terminal Block SV Combo Module

X5 Terminals (TB6)
23 1
TxD/RxD (-) RS-485 B
Internal 24 2
RS-485 A
Connection 25 3
TxD/RxD (+)
26 4
27 5
Signal Ground
6
7
= NPN Transistor 8
9
10
11
12
Figure 2. Example of wiring a Kongsberg Metering MPU 1200

ultrasonic flowmeter to an OMNI 6000 flow computer with
connections for serial data and live forward and reverse flow
signals (without pulse fidelity and integrity checking).
TB-010701B 23/27.73+ 7
Forward Flow Only with (Dual) Pulse Fidelity & Integrity

Checking
OMNI 6000 of serial data and forward flow signal, with connections for pulse
fidelity and integrity checking. In this example, assume that the OMNI has an E
module plugged into slot TB5, and an SV module in slot TB6.

Terminal Block E Combo Module Power Terminals

1 1 + + + + - - - -
Pulse Out 1A+
2 2
3 3
Pulse Out 1B+
4 4
5 5
Pulse In 3
6 6
Pulse In 4
7 7 2.2K to 10K
Ohm
8 8
9 9
Signal
10 10
Return
11 11
12 12
Terminal Block SV Combo Module

X5 Terminals (TB6)
23 1
Internal 24 2
RS-485 A
Connection 25 3
TxD/RxD (+)
26 4
27 5
Signal Ground
6
7
= NPN Transistor 8
9
10
11
12

connections for serial data, live forward flow signal, and
pulse fidelity and integrity checking.
8 TB-010701B 23/27.73+
Forward & Reverse Flow with (Dual) Pulse Fidelity &

Integrity Checking
OMNI 6000 of serial data and both forward and reverse flow signals, with
connections for pulse fidelity and integrity checking. In this example, the
OMNI has E modules in slots TB5 and TB6, and an SV module in slot TB7.

Terminal Block E Combo Module Power Terminals

1 1 + + + + - - - -
Pulse Out 1A+
2 2
3 3
Pulse Out 1B+
4 4
5 5
Pulse Out 2A+ Pulse In 3
6 6
Pulse In 4
7 7 2.2K to 10K
Pulse Out 2B+ Ohm
8 8
9 9
Signal
10 10
Return
11 11
12 12
E Combo Module
Terminals (TB6)
1
2
3
4
5
Pulse In 3
6
Pulse In 4
7 2.2K to 10K
Ohm
8
9
10
Signal Return
11
Terminal Block 12 SV Combo Module
X5 Terminals (TB7)
23 1
Internal 24 2
RS-485 A
Connection 25 3
TxD/RxD (+)
26 4
27 5
Signal Ground
6
7
= NPN Transistor 8
9
10
11
12

connections for serial data, live forward and reverse flow
signals, and pulse fidelity and integrity checking.
TB-010701B 23/27.73+ 9
MPU 1200 Configuration

MPU 1200 The following MPU 12000 miscellaneous configuration and serial port settings
Documentation are critical in communicating with the OMNI flow computer.
Always refer to the official
documentation supplied by
FMC Kongsberg when
Miscellaneous Configuration Settings
installing, configuring, and
operating the MPU 1200
Following are the corresponding MPU 1200 database object settings:
ultrasonic flowmeter.
Database Type: Object Number 788 – For Series A flowmeters, always
set to 1; where 0 = 32-bit single-precision and 1 = 64-bit double-precision
floating-point database. The Series B flowmeter database is fixed at 32-
bit single-precision.
Units of Measure: Object Number 798 – Set to the same units of
measure as OMNI 3000/6000 firmware; where 0 = metric and 1 =
Imperial (US) units.
Serial Port Settings

The MPU 1200 connects to an external system using the Modbus protocol via a
serial line. This connection is a 2-wire RS-485 serial link. You must also
configure the MPU 1200 serial port as follows:
MPU 1200 Serial Port Settings

Setting Assignment
Baud Rate 19.2K bps
Data Bits 8
Stop Bits 1
Parity None
Modbus ID 1
OMNI 3000/6000 Configuration

OMNI 3000/6000 Use either the flow computer’s front panel keypad or Omnicom configuration
Documentation PC software to enter configuration settings. The configuration settings specific
Reference to the MPU 1200 flowmeter are under the Miscellaneous Configuration Meter
For instructions on Run menu and the Meter Run Setup menu. Enter the miscellaneous meter run
configuring the OMNI flow
computer, see Chapter 2
settings first and then proceed to the meter run setup entries.
‘Flow Computer
Configuration’ in Volume 3
of the OMNI User Manual,
Miscellaneous Meter Run Configuration Settings
and the technical bulletin
TB-960701 ‘Overview of
Omnicom Configuration MPU 1200 ultrasonic gas flowmeter:
PC Software’.
Flowmeter Device Type – For each meter run, enter [6] to select the
Kongsberg Metering MPU 1200 flowmeter as the device type.
10 TB-010701B 23/27.73+
Flow I/O Point – Enter the input channel number that is used to input the
ultrasonic flowmeter pulse signal. Assign flowmeter pulse signals only to
Input Channels #3 and #4 of A and E combo modules, and input channel
#3 of a B combo module.
(Dual) Pulse Fidelity & Integrity Checking – Enter [Y] to enable pulse
fidelity and security checking for each meter run. Enter [N] to disable
dual pulse fidelity checking.
SV Module Port – The OMNI flow computer can accept two SV combo
modules. With one SV module, two SV ports are available, and with two
SV modules, four ports are available. For each ultrasonic meter run, enter
the SV port number (1 to 4) to which the SV module’s RS-485 serial
interface input from the MPU 1200 flowmeter is wired to the OMNI.
MPU Series B? (Y/N) – The OMNI flow computer can communicate
with the Series A flowmeter and beginning with v27.74.20 firmware, can
also communicate with the Series B flowmeter. Specify N for Series A or
Y for Series B.
Flow Direction – MPU 1200 flowmeters allow for bi-directional fluid
flow measurement. For pulse frequency signals, setup the flow computer
to totalize either forward or reverse flow on any meter run with an

The following meter run setup entries are available for the MPU 1200 ultrasonic
flowmeter when using pulse frequency signals:
Velocity of Sound Maximum Required Gain Value – The flow computer monitors the
The velocity of sound (VOS) maximum gain value for each ultrasonic path in both directions. An
refers to the amount of time alarm occurs if the gain of any path rises above this value.
it takes an acoustic pulse to
travel along the gas Minimum Burst Percent Used – This entry checks the ratio of valid
ultrasonic paths. The VOS
will vary depending upon
ultrasonic pulses received versus total pulses transmitted for each
gas type and line ultrasonic path in both directions. A ratio below this setting will cause an
conditions. alarm.
Velocity of Sound (VOS) in Gas, Deviation Percent from Average –
This entry is the maximum percent that the VOS of any individual path
can vary from the average VOS of all the paths. An alarm occurs if the
percent of deviation of one or more paths exceeds this value.
Maximum Flow Deviation Percent ⎯ If there is a valid flow I/O point
assigned, this is the percent of deviation between the calculated flow from
the pulse input channel compared to the MPU 1200 flow data received via
the OMNI SV serial port. The OMNI raises the pulse suspect alarm if the
flow deviation percentage exceeds this limit.
Maximum Meter Downtime ⎯ Enter the maximum allowable MPU
downtime in minutes. If communication downtime between the OMNI
and the MPU is less than this value, the OMNI will adjust its internal
totalizers to match the most recent MPU 1200 totalizer value.
TB-010701B 23/27.73+ 11
OMNI 3000/6000 Database Addresses &

Index Numbers
The following tables list the Modbus database addresses assigned within OMNI
firmware to the MPU 1200 ultrasonic metering feature. These tables categorize
data types.
Meter Run Alarm Status Points – Real Time Data

1 2 3 4 1 2 3 4
Loss of communication 2154 2254 2354 2454 T03 – Burst alarm 2172 2272 2372 2472
Loss of pulse impulse 2155 2255 2355 2455 T04 – Burst alarm 2173 2273 2373 2473
Flow rate delta alarm 2156 2256 2356 2456 T05 – Burst alarm 2174 2274 2374 2474
T00 - Gain high alarm 2157 2257 2357 2457 T07 – Burst alarm 2176 2276 2376 2476
T02 – Gain high alarm 2159 2259 2359 2459 T09 – Burst alarm 2178 2278 2378 2478
T05 - Gain high alarm 2162 2262 2362 2462 Path 0 - Gas VOS alarm 2181 2281 2381 2481
T11 - Gain high alarm 2168 2268 2368 2468 MPU 1200 status alarm(1) 2187 2287 2387 2487
T00 – Burst alarm 2169 2269 2369 2469 MPU 1200 config. Alarm(2) 2188 2288 2388 2488
T01 – Burst alarm 2170 2270 2370 2470 Notes: VOS Î Velocity of Sound
T02 – Burst alarm 2171 2271 2371 2471 Tnn Î Transducer nn
(1) This status alarm is active and logged in the OMNI 3000/6000 when Object No. 5 of the MPU 1200 Modbus
database is a non-zero value.
(2) This configuration alarm is active when Object No. 788 of the MPU 1200 Series A Modbus database is set to 0
(zero), enabling the 32-bit single-precision floating-point database. For the Series A flowmeter to
communicate with the OMNI 3000/6000, this object must always be set to 1, enabling the 64-bit double-
precision floating-point database. The Series B flowmeter is fixed at 32-bit single-precision floating point
database (see “MPU 1200 Configuration: Miscellaneous Configuration Settings” in this technical bulletin).
12 TB-010701B 23/27.73+
16-bit Integer Registers – Real Time Data

1 2 3 4 1 2 3 4
Flow direct. (0=frwd,1=rvrs) 3155 3255 3355 3455 T00 - Burst % used 3158 3258 3358 3458
T00 - Gain 3180 3280 3380 3480 T01 - Burst % used 3159 3259 3359 3459
T11 - Gain 3191 3291 3391 3491 Notes: Tnn Î Transducer nn
32-bit IEEE Floating Points – Real Time Data

1 2 3 4 1 2 3 4
Maximum % flow deviation 17513 17613 17713 17813 Path 2 - Velocity of sound 17529 17629 17729 17829
Maximum % VOS deviation 17516 17616 17716 17816 Path 3 - Velocity of sound 17530 17630 17730 17830
Velocity of sound (VOS) 17521 17621 17721 17821 Path 4 - Velocity of sound 17531 17631 17731 17831
Gas velocity 17522 17622 17722 17822 Path 5 - Velocity of sound 17532 17632 17732 17832
Gas flow rate 7101 7201 7301 7401 Path 0 - Gas velocity 17533 17633 17733 17833
Net flow rate 7102 7202 7302 7402 Path 1 - Gas velocity 17534 17634 17734 17834
Temperature 7105 7205 7305 7405 Path 2 - Gas velocity 17535 17635 17735 17835
Pressure 7106 7206 7306 7406 Path 3 - Gas velocity 17536 17636 17736 17836
Path 0 - Velocity of sound 17527 17627 17727 17827 Path 4 - Gas velocity 17537 17637 17737 17837
Path 1 - Velocity of sound 17528 17628 17728 17828 Path 5 - Gas velocity 17538 17638 17738 17838
TB-010701B 23/27.73+ 13

1 2 3 4 1 2 3 4
T00 - Gain 17543 17643 17743 17843 T00 - Gain 17574 17674 17774 17874
T01 - Gain 17544 17644 17744 17844 T01 - Gain 17575 17675 17775 17875
T02 - Gain 17545 17645 17745 17845 T02 - Gain 17576 17676 17776 17876
T03 - Gain 17546 17646 17746 17846 T03 - Gain 17577 17677 17777 17877
T04 - Gain 17547 17647 17747 17847 T04 - Gain 17578 17678 17778 17878
T05 - Gain 17548 17648 17748 17848 T05 - Gain 17579 17679 17779 17879
T06 - Gain 17549 17649 17749 17849 T06 - Gain 17580 17680 17780 17880
T07 - Gain 17550 17650 17750 17850 T07 - Gain 17581 17681 17781 17881
T08 - Gain 17551 17651 17751 17851 T08 - Gain 17582 17682 17782 17882
T09 - Gain 17552 17652 17752 17852 T09 - Gain 17583 17683 17783 17883
T10 - Gain 17553 17653 17753 17853 T10 - Gain 17584 17684 17784 17884
T11 - Gain 17554 17654 17754 17854 T11 - Gain 17585 17685 17785 17885
Path 0 - Gas velocity 17555 17655 17755 17855 Path 0 - Gas velocity 17586 17686 17786 17886
Notes: Tnn Î Transducer nn
Flow Computer Configuration Data – Miscellaneous Meter Run Configuration

1 2 3 4 1 2 3 4
Flowmeter device type 3108 3208 3308 3408 Flow direct. (0=frwd,1=rvrs) 3155 3255 3355 3455
Maximum downtime (min) 3116 3216 3316 3416 Flow pulse freq. I/O pnt. # 13001 13014 13027 13040
SV module port # 3153 3253 3353 3453 MPU 1200 Series A or B 3154 3254 3354 3454
(0 = Series A, 1 = Series B)
Flow Computer Configuration Data – Meter Run Setup

1 2 3 4 1 2 3 4
Max. gain value (0 to 11) 17513 17613 17713 17813 Minimum burst % used 17515 17615 17715 17815
Maximum % flow deviation 17514 17614 17714 17814 Maximum % VOS deviation 17516 17616 17716 17816
14 TB-010701B 23/27.73+
OMNI 3000/6000 User Displays

Meter Run Data
Meter Run Data Display To view the meter run data on the flow computer LCD display, press [Meter]
The meter run data that is [n] [Display] on the OMNI front panel keypad when in the Display Mode (“n”
displayed on OMNI screens equals the meter run number: 1 to 4). The following data will display:
corresponds to the SV port
number the user assigned
to each meter run during
OMNI flow computer METER #n
configuration (see section Log Data Count
“OMNI 3000/6000 Software Revision yymmdd
Configuration: Flow Velocity m/s
Miscellaneous Meter Run Actual Volume Flowrate m3/h
Configuration Settings”). Velocity of Sound m/s
Forward Flow m3
Reverse Flow m3
Units of Measure Line Pressure Bar
Displayed on OMNI Line Temperature °C
3000/6000 Screens Internal Pipe Diamter mm
Both the MPU 1200 and the Rate Corr. Factor A (Neg Dir.) XX
OMNI 3000/6000 must have Rate Corr. Factor B (Neg Dir.) XX
firmware that supports the Rate Corr. Factor A (Pos Dir.) XX
same units of measure; i.e., Rate Corr. Factor B (Pos Dir.) XX
both devices either have Flow Velocity Cut-off Limit m/s
metric firmware or U.S. Alarm Status X
firmware. The types of units FlowV P0 m/s
are: FlowV P1 m/s
Variable US Metric FlowV P2 m/s
FlowV P3 m/s
Temperature °F °C FlowV P4 m/s
Pressure(abs.) PSIa Bara FlowV P5 m/s
Totals ft
3
m
3
VOS P0 m/s
Flow Rate
3
ft /h
3
m /h VOS P1 m/s
VOS P2 m/s
Velocity ft/s m/s VOS P3 m/s
VOS P4 m/s
VOS P5 m/s
Burst% P0-11 XXX-XXX
Burst% P2-9 XXX-XXX
Burst% P3-8 XXX-XXX
Burst% P4-7 XXX-XXX
Burst% P5-6 XXX-XXX
Burst% P6-5 XXX-XXX
Burst% P7-4 XXX-XXX
Burst% P8-3 XXX-XXX
Burst% P9-2 XXX-XXX
Gain P0-11 XXXX-XXXX
Gain P2-9 XXXX-XXXX
Gain P3-8 XXXX-XXXX
Gain P4-7 XXXX-XXXX
Gain P5-6 XXXX-XXXX
Gain P6-5 XXXX-XXXX
Gain P7-4 XXXX-XXXX
Gain P8-3 XXXX-XXXX
Gain P9-2 XXXX-XXXX
TB-010701B 23/27.73+ 15
SV Module Serial Port

SV Port Data Display You can view live data received via RS-485 communications on the flow
The SV port data that is computer front panel LCD display only if a SV port is used to input the RS-485
displayed on OMNI screens interface from the MPU 1200 flowmeter. To view this raw data, press [Setup]
is specific to each SV port [n] [Display] on the OMNI front panel keypad when in the Display Mode (“n”
only, as acquired from the
MPU 1200. equals the SV port number: 1 to 4). The following data displays:
MPU 1200 Serial Port SV Port n MPU 1200

Settings Software Revision yymmdd
Log Data Count …X…
To communicate with the
Flow Velocity m/s
OMNI 3000/6000, set the
Actual Volume Flowrate m3/h
MPU 1200 as follows:
Forward Flow m3
Setting Assign Reverse Flow m3
Baud Rate 19.2K bps Line Pressure (Absolute) Bara
Data Bits 8 Line Temperature °C
Internal Pipe Diamter mm
Stop Bits 1
Rate Corr. Factor A (Neg Dir.) m3
Parity None Rate Corr. Factor B (Neg Dir.) m3
Modbus ID 1 Rate Corr. Factor A (Pos Dir.) m3
Rate Corr. Factor B (Pos Dir.) m3
Flow Velocity Cutoff Limit m/s
Units of Measure Alarm Status X
Displayed on OMNI Flow Velocity - Path 0 m/s
3000/6000 Screens Flow Velocity - Path 1 m/s
Both the MPU 1200 and the Flow Velocity - Path 2 m/s
OMNI 3000/6000 must have Flow Velocity - Path 3 m/s
firmware that supports the Flow Velocity - Path 4 m/s
same units of measure; i.e., Flow Velocity - Path 5 m/s
both devices either have Velocity of Sound - Path 0 m/s
metric firmware or U.S. Velocity of Sound - Path 1 m/s
firmware. The types of units Velocity of Sound - Path 2 m/s
are: Velocity of Sound - Path 3 m/s
Variable US Metric Velocity of Sound - Path 4 m/s
Velocity of Sound - Path 5 m/s
Temperature °F °C
Burst % - T00ÆT11 XXX-XXX
Pressure(abs.) PSIa Bara Burst % - T01ÆT10 XXX-XXX
Totals ft
3
m
3
Flow Rate
3
ft /h m /h
3 Burst % - T03ÆT08 XXX-XXX
Velocity ft/s m/s
Gain - T00ÆT11 XXXX-XXXX
16 TB-010701B 23/27.73+
TB-020101G OMNI Serial/Modbus Mux Module 68-6209: Setup & Installation
When configuring the Omni from the onboard DB9 serial

port and using the backspace key, data was not displayed
properly on the input line.
v1.25 Ethernet Menu - Allow escape key when entering the
Ethernet ID. Changed the text from "Modbus Port" to
"Encap. Modbus Port".
Security Menu - Allow escape key when entering MAC
addresses.
Debug Menu - Added "Debug Ethernet" and "Debug
Repeater" selections.
All menus - Backspace displayed garbage on the screen.
Added the ability to obtain and reset the Telnet Port via UDP
before a Configuration session (available with Network
Utility v1.07 and up).
Added an "Inactivity" message when in the Debug mode if
the Modbus communication's socket is closed due to Modbus
inactivity time out.
The 5-minute Telnet time out timer is refreshed every time a
debug message is printed during Modbus communications.
This change allows continuous debug data to be captured
without timing out. After 5 minutes of Modbus inactivity, the
Telnet session will time out.
Preset Single Register (function code 06) was not properly
handling 32-bit long integers and floats writes and resulted in
a short message sent to the flow computer and thus incorrect
values written.
Added a refresh of the configured Netmask and Gateway
when the IP address is changed.
Removed the setting of the Netmask based on class when the
IP address was changed via the "Set IP Address" feature in
Network Utility.
Removed the ping of the IP address configured in the SE
module in order to update ARP tables on network devices
when replacing an SE module using the same IP address as
the previous SE module. It now pings the configured
Gateway IP address instead of the local IP address.
The ARP table entries for the Ethernet devices on the local
subnet are already updated automatically when a new session
is initiated with the SE module.
Removed the 5 second time delay at start up before being
able to establish communications after power up or Board
TB-020101G  All Revisions 37

Reset and now it just waits for the sockets to initialize before
communications is allowed.
enough extended memory it will free the memory used for the
Syslog.
v1.24 Ethernet Menu - Added a 15 character "Eth ID". The ID can
be used to name or describe the Ethernet Module. Removed
the "Set IP via Ping" flag.
Host Menu - Baud Rate - 57600 was removed from the Host
choices.
Remote Menu - Baud Rate - 57600 was listed as a choice but
when selected gave an "Invalid Parameter" message. 57600
was enabled as a valid selection.
Security Menu - Added a "Respond to Ping" flag. The
choices are (0)Disabled (1)Enabled. The default is Enabled.
Allow MAC addresses to be entered with corresponding
hyphens between numbers.
System Info Menu - Modicon compatibility is auto-detected
on start up and the status is displayed as Enabled or Disabled.
Logging Menu - Added the System Logging menu and
functionality (Syslog).
Added an ICMP Handler to handle pings.
The IP Address can no longer be configured using the "arp -
s" command.
Added a 5 second time delay after restart to allow the Omni
to initialize.
If the physical connection to the OMNI was broken, the
connections were remaining open. Now all connections are
closed when the physical link is detected broken. When the
link is re-established, it is logged to the System Log (if
enabled).
SE Module responded to a ping if the MAC address matched
but was not checking that the IP address matched as well.
The check for the TCP password is now skipped on messages
going through the repeater port.
Connections via the serial port at the same time as a Telnet
connection was causing the configuration menu display to
lock up and time out at the PC side.

TB-020101G OMNI Serial/Modbus Mux Module 68-6209: Setup & Installation
Configuration menu display was stopping before end of menu

when using Telnet.
Debug All not keeping up on long (255 bytes) messages.
Display a message to the user if Debug mode is selected
when on a serial connection.
v1.23 Added „Advanced‟ and „Debug‟ entries to the menu. Added
new parameters in the Advanced menu to help with TCP/IP
over VSAT. Minimum and Maximum retry on packets
retransmission as well as the ability to turn the Nagle
Algorithm on or off was added. Debug was placed on menu
instead of typing 'X' or 'Z'.
v1.22 Removed ICMP handler - use library instead. IP change via ping
is permanent.
v1.21 Added disable of ICMP (Ping) and further checks in the ICMP
handler.
v1.20 Changed tasks to speed up. Added debug through Telnet with 'X'
and 'Z'. Added Flash download support.
v1.10 Corrected a problem with Modbus/TCP queued requests getting
ignored.
v1.09 Added keepalive to detect dropped connections when the
inactivity time out is set to zero. Added a „Reset‟ on the serial
and telnet menus to reset the ethernet board via telnet.
v1.08 Added ICMP Handler and fixed the handling of unknown
Modbus function codes so they fall through untouched. Added
tcp_tick in handlers to detect if a socket is closed in the middle of
a transaction. Added „exit‟ on the serial and telnet menus.
v1.07 Removed Modbus Delay parameter. Added the ability to set a
Temporary IP address using arp and ping on a PC so serial
connection is not required. Change the default Subnet Mask to
Class A 255.0.0.0.
v1.06 Fixed bug when changing TCP Port where it didn't take effect
until reset.
v1.05 Added ping to clear up arp tables.
v1.04 Padded connection buffers.
v1.03 Minor Menu Changes.
v1.02 Enabled the gateway parameter.
v1.01 Initial Version

Date: 08 28 02 Author(s): I. P. TB-020501
Communicating with Daniel Ultrasonic Gas

Flowmeter Model 3400, SeniorSonic
Communicating with
Daniel Ultrasonic Gas
Contents
Flowmeter Model 3400,
SeniorSonic
Scope .......................................................................................................1
This technical bulletin Abstract ...................................................................................................2
Daniel SeniorSonic 3400 Ultrasonic Flowmeter
Manual, applicable to Theory of Operation................................................................................2
Revision 23.73/27.73+.
Omni Flow Computer Logic ...................................................................2
The Daniel Senior Sonic
ultrasonic flowmeter Modbus Communication ........................................................................4
measures gas flow by using
the Time Travel method of Wiring Installation...................................................................................4
acoustic pulses. This Omni Combo Module Terminal Assignments ..................................................5
device communicates with
Omni flow computers via Senior Sonic Terminal Assignments .................................................................7
Omni’s ‘SV’ process I/O
combo module using a
Forward & Reverse Flow Signals .....................................................................7
proprietary protocol. To use Forward Flow Only with (Dual) Pulse Fidelity & Integrity Checking..............9
the scaled pulse output of
the Daniel Senior Sonic Forward & Reverse Flow with (Dual) Pulse Fidelity & Integrity Checking...10
Metering, the flow computer Omni Flow Computer Configuration ...................................................11
must at least either have an
‘A’, ‘B’ or ‘E’ combo module Miscellaneous Configuration Meter Run Settings ..........................................11
installed.
Meter Run Setup Entries .................................................................................12
Getting Tech Support Omni Flow Computer Database Addresses & Index Numbers.........13
Omni Technical support is Omni Flow Computer User Displays...................................................15
available at: SV Module Serial Communications Port ........................................................15
Phone: (281) 240-6161 Meter Run Data ...............................................................................................16
Fax: (281) 240-6162
Scope
www.omniflow.com
or send email to: This technical bulletin applies to firmware revisions 23.73+ and 27.73+ of
techsupport@omniflow.com Omni 6000/Omni 3000 flow computers, for gas flow metering systems.
TB-020501 23/27.73+ 1
Abstract
The Daniel SeniorSonic ultrasonic flowmeter determines the linear gas velocity
through the meter tube by using multiple acoustic pulse paths. The flowmeter
analyzes these paths employing the delta time travel measurement method. The
Omni flow computer either totalizes the flowmeter pulse input signal or
determines the flowrate from the data received serial from the flowmeter.
SeniorSonic Ultrasonic Flowmeter

Theory of Operation
Daniel's ultrasonic gas flow-metering technology incorporates multiple pairs of
transducers into a smart digital inferential instrumentation device. This device
is installed into a gas pipeline system to measure gas flow. Each pair of
Four pairs of transducers are positioned across the meter so that the path
upstream relative to the other. Pulses emitted by the downstream transducer are
slowed down by the velocity of the fluid, with flow the pulse takes longer to
travel to the upstream transducer than with no flow. Pulses emitted by the
upstream transducer are aided by the velocity of the fluid, with flow the pulse
takes less time to travel to the downstream transducer. Ultrasonic flowmeters
such as the SeniorSonic 3400, that apply delta time methodology, measure these
two travel times to determine both the linear fluid velocity and the speed of
sound in the fluid. The flowmeter can measure fluid velocity for bi-directional
(forward/reverse) fluid flow.
Omni Flow Computer Logic

The Omni flow computer can determine the actual flow rate from data received
either serially from the SeniorSonic flowmeter, or from a live pulse frequency
signal input if one has been connected, assigned, and configured. In this
application, Modbus serial communication can be configured as the primary
measurement source with the pulse frequency configured as the backup
measurement source or vice versa to determine the actual flow rate. The Omni
flow computer can also be configured to use only the Modbus serial
communication link with no pulse frequency input. When Modbus
communications are available the flow computer transmits flowing temperature
and pressure to the flowmeter to enable it to correct spool dimensions.
The flowmeter serially transmits the accumulated volume to the Omni. The
flow computer obtains a calculated volume increment by subtracting the new
accumulated volume from the last accumulated volume it received. The
flowmeter updates its totalizers on a regular interval depending upon flowing
conditions and configuration settings. Updating the Omni totalizers on this
same period would result in somewhat erratic totalizers and sampler pulse
2 TB-020501 23/27.73+
TB-020501 Communicating with Daniel Ultrasonic Gas Flowmeter Model 3400, SeniorSonic
The Omni provides a smooth totalizer update by monitoring the time interval
between SeniorSonic totalizer updates, and distributing the volume increment
over a matching time-period.
Start
Is
SV Serial Set SeniorSonic
Communications No Communication
OK Failed Alarm
?
Yes
Is
Clear SeniorSonic
Communication
Assigned Yes Suspect Alarm
Failed Alarm
?
No
Is
Transmitter
Flowrate in Correct Disable Totalizing
No Pulse Input Signal
Direction
?
Yes
Is
Assigned No Suspect Alarm
? Set Meter Run
Not Active
Yes
Is SV
Communications Calculate Flow
Primary No Based on Pulses
?
Yes
Calculate Flow
Based on SV Link
Compare Flow
Based on Pulses to
Serial Data Flow
Is
Flow
Set Pulse Signal
Comparison
No Suspect Alarm
within Limits
?
Yes
Clear Pulse Signal

Suspect Alarm

Transmitted Serial Data
End
Figure 1. Flow computer logic flow diagram for the Daniel SeniorSonic
3400 ultrasonic gas flowmeter.
TB-020501 23/27.73+ 3
In the event of a communication failure between the two devices, the Omni will
not receive serial data. However, the SeniorSonic may be fully operational and
continue to accumulate volume. In this case, if a pulse signal is available from
the flowmeter and the Omni flow computer is configured to receive the flow
pulse signal as a backup, the flow computer will automatically continue to
necessary to match the SeniorSonic internal totalizer. The flow computer
automatically adjusts its totalizers to account for the small amount of flow that
takes place before it detects that a communication failure has occurred (i.e., the
Omni does not immediately start totalizing using the SeniorSonic pulse train).
If a pulse signal from the SeniorSonic is not available, and the communication
link fails, the flow computer immediately stops totalizing. Once
communication is reestablished, the Omni will adjust its internal totalizers to
match the SeniorSonic totalizer. In this case, the Omni may have to add a
significant amount of flow to its totalizers, depending upon how much time the
communication link was inoperative.
In some instances, adjusting the flow computer’s totalizers may not be

desirable; e.g.: if a flowmeter has been disconnected for a long period of time,
or the SeniorSonic electronics package has been replaced. For these cases, there
are flow computer configuration settings that specify the maximum time that a
SeniorSonic serial communication failure can exist, and still be compensated for
by adjusting the flow computer totalizers. By default, this maximum time is 15
minutes.
Modbus Communication
Serial Data The SeniorSonic connects to an external system using the Modbus ASCII
Communications protocol via a serial line. This connection is typically a 2-wire RS-485 serial
The serial interface between link. Communications parameters are fixed in the Omni at:
these devices is 2-wire RS-
modified Modbus protocol.
Omni Flow Computer Fixed Communications Parameters

Setting Up and Wiring
to Omni Combo Setting Value
Modules Baud Rate 9600
In order to communicate Data Bits 7
with Daniel Senior Sonic Stop Bits 1
ultrasonic flowmeters, the
Omni flow computer must
Parity Even
be equipped with at least Protocol Modbus ASCII
one SV combo module
(Model 68-6203). For
instructions on jumper
settings and other process
I/O combination module
Wiring Installation
refer to Volume 1, Chapter
2 of the Omni User Manual There are several options for wiring a SeniorSonic ultrasonic meter to an Omni
flow computer. The option to implement depends upon requirements of the
flow metering system.
4 TB-020501 23/27.73+
Always interconnect these devices via a 2-wire RS-485 serial interface from the
SeniorSonic to an Omni SV combo module serial port. This connection uses
the Modbus protocol to transmit to the Omni the volumetric flow data that the
SeniorSonic accumulates. The Omni also transmits the fluid temperature and
pressure to the flowmeter to allow the flowmeter to correct for dimensional
changes of the measurement Spool.
In addition to serial data, the Omni can also receive live forward and/or reverse
flow pulse signals from the SeniorSonic. The SeniorSonic transmits pulse
frequencies through wires typically connected to an Omni E combo module.
Connecting two SeniorSonic pulse output channels to the Omni can provide
pulse fidelity and integrity checking. To perform pulse fidelity checking, the
Omni must have one E combo module for each flow direction requiring
totalization.
Omni Combo Module Terminal Assignments

Depending upon the implemented wiring option, the Omni requires SV, E,
and/or A combo modules. The tables below specify the terminal assignments
for each module type. This information is necessary when connecting wires to
the Omni. The terminal block number (TBn) on the Omni back panel for each
combo module corresponds to the slot on the motherboard into which the
module is plugged. For more information, see “Volume 1: System Architecture
and Installation” of the Omni User Manual.
Omni SV Combo Module Back Panel Terminal Assignments (TBn)

1 Port # 1 (3): RS-485 B Wire
2 Port # 1 (3): RS-485 A Wire
3 Port # 2 (4): RS-485 B Wire
4 Port # 2 (4): RS-485 A Wire
Note: Numbers in parenthesis “( )” refer to SV module 2 if installed.
TB-020501 23/27.73+ 5
Omni E Combo Module Back Panel Terminal Assignments (TBn)

Signal Return for Terminals 5, 6, 7, 8, 9, 11 & 12 (Internally connected to
10
DC power return
Omni A Combo Module Back Panel Terminal Assignments (TBn)

Signal Return for Terminals 9, 11 & 12 (Internally connected to DC power
10
return
Analog Output # 2: 4-20mA or RTD Excitation Current Source Output #2
12
(See JP12 Setting)
6 TB-020501 23/27.73+
SeniorSonic 3400 Terminal Assignments

Use the two P2 terminal blocks in the Senior Sonic to connect to the Omni. The
tables below specify the terminal assignments for each of these terminal blocks.
This information is necessary when connecting wires to the Senior Sonic.
SeniorSonic 3400 Electronics Board Terminal Block P2

Assignments
1 DIG GND (Negative)
2 DIG GND (Negative)
3 FREQ1A Fwd Flow Pulses (Positive)
4 FREQ1B Fwd Flow Fidelity Pulses (Positive)
5 FREQ2A Rev Flow Pulses (Positive)
6 FREQ2B Rev Flow Fidelity Pulses (Positive)
7 N/A
8 N/A
9 N/A
10 N/A
11 N/A
12 N/A
SeniorSonic Peripherals Terminal Block P2 Assignments

12 Signal Ground
11 RS-485- (Negative)
10 RS-485+ (Positive)
*9 Signal Ground
*8 RS-485- (Negative)
*7 RS-485+ (Positive)
Note* 12, 11, and 10 are internally connected to 9, 8, and 7
TB-020501 23/27.73+ 7

Shown below is a typical wiring installation between the Daniel SeniorSonic
and an Omni 6000 for serial data and both forward and reverse flow signals. In
this example, assume that the Omni 6000 has an A module plugged into slot
TB5, and an SV module in slot TB6.
DANIEL SENIOR SONIC OMNI FLOW COMPUTER

P2 Electronics Peripheral
A Combo Module Terminals (TB5)
Field Connection Board
DIG-GND 1 1
DIG-GND 2 2
(FWD)
FREQ1A 3 3
FREQ1B 4 4
(REV) Pulse In
FREQ2A 5 5
Return 3rd Input Channel
FREQ2B 6 6
Pulse In
7 7
Return 4th Input Channel
8
9
10
11
16 12
Electronics Terminal Board SV Combo Module Terminals (TB6)

RS485C 12 1 RS-485 - (B)
Port #1
RS-485- 11 2 RS-485 +(A)
RS-485+ 10 3 RS-485 - (B)
Port #2
RS-485C 9 4 RS-485 +(A)
RS-485- 8 5
RS-485+ 7 6
6 7
5 8
4 9
3 10
2 11
1 12
Figure 2. Example of wiring a Daniel SeniorSonic 3400 ultrasonic

flowmeter to an Omni 6000 flow computer with connections
for serial data and live forward and reverse flow signals
(without pulse fidelity and integrity checking).
8 TB-020501 23/27.73+
Forward Flow Only with (Dual) Pulse Fidelity & Integrity

Checking
Shown below is a typical wiring installation between the Daniel SeniorSonic
and an Omni 6000 for serial data and forward flow signals, with connections for
pulse fidelity and integrity checking. In this example, assume that the Omni
6000 has an E module plugged into slot TB5, and an SV module in slot TB6.

P2 Electronics Peripheral
E Combo Module Terminals (TB5)
Field Connection Board
1 1
DIG-GND
2 2
DIG-GND
FWD (A)
3 3
FREQ1A
FWD (B)
4 4
FREQ1B Pulse In
5 5 3rd Input Channel
FREQ2A Pulse In
6 6 4th Input Channel
FREQ2B
7 7
8
9
Signal
10
Return
11
16 12
Electronics Terminal Board SV Combo Module Terminals (TB6)

RS-485C 12 1 RS-485- (B)
Port#1
RS-485- 11 2 RS-485+(A)
RS-485+ 10 3 RS-485- (B) Port#2
RS-485C 9 4 RS-485+(A)
RS-485- 8 5
RS-485+ 7 6
6 7
5 8
4 9
3 10
2 11
1 12

for serial data, live forward flow signal, and pulse fidelity and
integrity checking.
TB-020501 23/27.73+ 9
Forward & Reverse Flow with (Dual) Pulse Fidelity &

Integrity Checking
Shown below is a typical wiring installation between the SeniorSonic and an
Omni 6000 for serial data and both forward and reverse flow signals, with
connections for pulse fidelity and integrity checking. This example assumes
that the Omni 6000 has two E modules in slots TB5 and TB6, and an SV
module in slot TB7.

P2 Electronic Peripherial
Field Connection Board E Combo Module Terminals (TB5)
DIG-GND 1 1
DIG-GND 2 2
FREQ1A 3 3
FWD
FREQ1B 4 4
Pulse In
FREQ2A 5 5 3rd Input Channel
REV Pulse In
FREQ2B 6 6 4th Input Channel
7 7
8 8
9 9
Signal Return
10 10
11 11
12 12
13
E Combo Module Terminals (TB6)
14
15 1
16 2
3
4
Pulse In
5 3rd Input Channel
Pulse In
6 4th Input Channel
7
8
9
Signal Return
10
11
12
Electronics Termnial Board
SV Combo Module Terminals (TB7)
RS-485C 12 1 RS-485- (B)
Port#1
RS-485- 11 2 RS-485+(A)
RS-485+ 10 3 RS-485- (B)
Port#2
RS-485C 9 4 RS-485+(A)
RS-485- 8 5
RS-485+ 7 6
6 7
5 8
4 9
3 10
2 11
1 12

for serial data, live forward and reverse flow signals, and
pulse fidelity and integrity checking.
10 TB-020501 23/27.73+
Omni Flow Computer Configuration

Use the flow computer’s front panel keypad to enter configuration settings unique to
the SeniorSonic Flowmeter. The configuration settings that are specific to the
SeniorSonic flowmeter are under Miscellaneous Setup, Configure Meter Run menu
and the Meter Run Setup menu. Enter the miscellaneous configuration meter run
settings first and then proceed to the meter run setup entries (see Chapter 2 ‘Flow
Computer Configuration’ in Volume 3 of the Omni User Manual, and the technical
bulletin TB-960701 ‘Overview of OmniCom Configuration PC Software’).

SeniorSonic ultrasonic gas flowmeter:
Select Flowmeter Device Type – For each meter run, enter [8] to select the
Daniel Ultrasonic flowmeter as the device type.
Select SV Module Port – The Omni flow computer can accept two SV
combo modules. With one SV module, two SV ports are available, and with two
SV modules, four ports are available. For each ultrasonic meter run, enter the SV
port number (1 to 4) to which the SV module’s RS-485 serial interface input from
the SeniorSonic flowmeter is wired to the Omni.
DFI Address – This is the address ID of the Daniel ultrasonic flowmeter

communications port.
DFI Retry – This is the number of SV serial port communications retries

the Omni will attempt with the flowmeter after a communications failure before
actually raising a communications fail alarm.
Flow I/O Point – Enter the input channel number that is used to input the
ultrasonic flowmeter pulse signal. Assign flowmeter pulse signals only to Input
Channels #3 and #4 of A or E combo modules, or input channel #3 of a B combo
module.
Select Flow Direction (F/R) – SeniorSonic flowmeters allow for bi-

directional fluid flow measurement. For pulse frequency signals, setup the flow
computer to totalize either forward or reverse flow on any meter run with an
TB-020501 23/27.73+ 11
Primary Flow – This setting instructs the Omni flow computer to use
either the pulse input channel or the SV serial communications data as the
primary means of calculating flow. Options are:
0 = Select Serial Data as primary flow. This means that the SV serial
communications data will be the primary and the pulse input channel, if
assigned, will be used as a backup means of flow calculations by the
flow computer.
1 = Select Pulse Input as primary flow. This means that the flow pulses
received from the flowmeter will be the primary and the SV serial
communications data will be used as a backup means of flow
calculations by the flow computer.

The following meter run setup entries are available for the SeniorSonic
ultrasonic flowmeter when using pulse frequency signals:
Difference Between
Velocity of Sound (VOS) in Gas, Deviation Percent from Average – In
‘Gas Velocity’ and
‘Velocity of Sound’ some configurations, the flow computer can verify that the average VOS
calculated for all paths conforms to the VOS of each individual path. This
The ‘velocity of sound’
(VOS) refers to the amount entry is the maximum percent that any one path VOS varies from the
of time it takes an acoustic average VOS of all the paths.
pulse to travel along the gas
ultrasonic paths. The VOS
will vary depending upon Flow Minutes – The time interval can be set for comparing the flow pulses
gas type and line input flow with the SV communications serial link flow. If the flow
conditions.
deviation exceeds the Flow Deviation Percent setting (see next setting) when
this comparison is made, the Omni will switch from the primary (flow pulses
or SV serial link) to the backup source (SV serial link or flow pulses) for
calculating flow. (Note: Daniel Industries recommends a minimum of 60
minutes for this setting due to the fluctuating flow pulse frequency output by
the flowmeter.)
Maximum Flow Deviation Percent  Only valid if a flow pulses I/O

point is assigned -, this is the allowable percent of deviation between the
calculated flow from the pulse input channel compared to the SeniorSonic
flow data received via the Omni SV serial port. The Omni raises the pulse
suspect alarm if the flow deviation percentage exceeds this limit. Note: See
the Flow Minutes setting previous.
12 TB-020501 23/27.73+
Maximum Meter Downtime  Enter the maximum allowable flowmeter

downtime in minutes. If communication downtime between the Omni and
the SeniorSonic is greater than this value, the Omni will not adjust its
internal totalizers to match the most recent SeniorSonic totalizer value.
Depending upon how much time the communication link and pulses were
inoperative and the amount of flow that occurred during this downtime,
when communications is reestablished within the time specified in this
setting, the Omni may have to add a significant amount of flow to its
totalizers. (Default = 15)
Omni Flow Computer Database

Addresses & Index Numbers
The following tables list the Modbus database addresses assigned within Omni
firmware to the SeniorSonic ultrasonic metering feature. These tables
categorize data type.

Database Address
Description For Meter Run Number
1 2 3 4
Loss of communication 2154 2254 2354 2454
Loss of pulse input 2155 2255 2355 2455
Flow rate deviation alarm 2156 2256 2356 2456
Path 0 - Gas VOS alarm 2181 2281 2381 2481

Database Address
Description for Meter Run Number
1 2 3 4
TB-020501 23/27.73+ 13

1 2 3 4 1 2 3 4
Serial Gross flow during Flow 17141 17151 17161 17171 Temperature 7105 7205 7305 7405
Minutes period
Pulses Gross flow during Flow 17142 17152 17162 17172 Pressure 7106 7206 7306 7406
Minutes period
Calculated Flow Dev % 17143 17153 17163 17173 Velocity of sound A 17527 17627 17727 17827
Maximum flow deviation (%) 17513 17613 17713 17813 Velocity of sound B 17528 17628 17728 17828
Total from serial link (prev) 17213 17217 17221 17225 Velocity of sound C 17529 17629 17729 17829
Total from serial link 17214 17218 17222 17226 Velocity of sound D 17530 17630 17730 17830
Total from pulse input 17215 17219 17223 17227
Dev % between serial & pulse 17216 17220 17224 17228 Gas velocity A 17533 17633 17733 17833
Maximum VOS deviation (%) 17516 17616 17716 17816 Gas velocity B 17534 17634 17734 17834
Velocity of sound (VOS) 17521 17621 17721 17821 Gas velocity C 17535 17635 17735 17835
Gas velocity 17522 17622 17722 17822 Gas velocity D 17536 17636 17736 17836

1 2 3 4 1 2 3 4
Gas velocity A 17556 17656 17756 17856 Gas velocity A 17587 17687 17787 17887
Gas velocity B 17557 17657 17757 17857 Gas velocity B 17588 17688 17788 17888
Gas velocity C 17558 17658 17758 17858 Gas velocity C 17589 17689 17789 17889
Gas velocity D 17559 17659 17759 17859 Gas velocity D 17590 17690 17790 17890

1 2 3 4 1 2 3 4
Flow pulse I/O point # 13001 13014 13027 13040 DFI Retry Times 3156 3256 3356 3456
Flowmeter device type 3108 3208 3308 3408 Primary Flow 3157 3257 3357 3457
SV module port # 3153 3253 3353 3453 (0=Serial, 1=Pulses)
DFI Address 3154 3254 3354 3454 DFI Delay Timer 13445 13446 13447 13448

1 2 3 4 1 2 3 4
Meter maximum downtime 3116 3216 3316 3416 Maximum VOS deviation (%) 17516 17616 17716 17816
(minutes) Daniel Ultrasonic K-factor 17538 17638 17738 17838
Maximum flow deviation (%) 17513 17613 17713 17813 Minimum burst % 17515 17615 17715 17815
14 TB-020501 23/27.73+
Omni Flow Computer User Displays

interface from the SeniorSonic flowmeter. To view this data, press [Setup] [n]
[Display] on the Omni front panel keypad (where “n” equals the SV port
number 1 to 4, you want to display), when in the Display Mode. The following
data will display:
TB-020501 23/27.73+ 15
Meter Run Data

To view the meter run data on the flow computer LCD display, press [Meter]
[n] [Display] on the Omni front panel keypad (where “n” equals the meter run
number, 1 to 4, you want to display), when in the Display Mode. The following
data will display:
16 TB-020501 23/27.73+
Operating the Suitcase Prover

Bi-Directional Pipe Configuration
Contents
User Manual Reference - Scope................................................................................................................... 1
information contained in Getting Started ................................................................................................... 3
Volume 1-4, applicable to
OmniCom Configuration Files ................................................................................................... 3
firmware revisions 20 & 24.
Step 1 - Create Generic Configuration Files for Each Prover ..................................................... 3
Step 2 - Create a Configuration File for Each Flowmeter to be Calibrated ................................. 3
Step 3 – Connect the Prover Computer to the Prover................................................................. 3
Step 4 – Transmit the Flowmeter Specific Configuration File to the Prover Computer ............... 3
Step 5 – Operate the Prover Computer and Calibrate the Flowmeter ........................................ 3
Using the OmniCom Software to run the Prover ....................................................................... 4
Step 6 - Printing and Saving the Flowmeter Calibration Prove Report ....................................... 5
Step 7 – Saving the Report ......................................................................................................... 6
Filenames Compatible to those Created by DOS OmniCom ......................... 6
Descriptive Filenames Created for use with Windows OS ............................ 6
available at:
(281) 240-6161
Scope
the WEB Page at:
This technical bulletin contains supplementary information relating to the operation and
www.omniflow.com
use of the Omni Flow Computer Suitcase Prover Computer. Basic knowledge of the
or email to:
Omni flow computer and how to operate the OmniCom program is assumed. If the
information you require is not contained in this document refer to the Omni Flow
Computer Manual (Volumes 1 through 4) or additional technical bulletins contained on
the CD-ROM provided with the equipment. Help on OmniCom can be found in the
OmniCom Quick Start Guide provided on the OmniCom installation CD-ROM.
TB-060327 Only Revs 20.74+ & 24.74+ 1

Abstract
The Omni Suitcase Prover Computer is a customized application of the Omni 3000
Flow Computer. The flow computer is mounted to a control panel that is resiliently
mounted within a fiberglass suitcase. The internal surfaces of the suitcase are coated
with a conductive flexible shielding material for static electricity protection and RF
shielding purposes. The suitcase provides a convenient package that is both rugged
and portable.
The control panel contains the following items:

1) Omni 3000 Flow Computer
2) through 7) - Six Lighted Push Button Switches to operate the connected prover system.
a. Detector Switch Status *
b. 4 Way Valve Seal Status *
c. Launch Forward Command Status *
d. Launch Reverse Command Status *
e. Prove Request/Abort
f. Report Reprint
* In addition to indicating status conditions, pressing these buttons forces the
appropriate signal to be active for testing and override purposes.
8) 9 pin RS232C male connector to printer
9) 9 pin RS232C female connector to Computer (Modbus Protocol)
10) MS connector (A) Prover wiring (see Omni drawing # 20900100 sheet 2 of 2)
11) MS connector (B) Prover wiring (see Omni drawing # 20900100 sheet 2 of 2)
12) MS connector (C) Test Meter wiring (see Omni drawing # 20900100 sheet 2 of 2)
13) MS connector (D) Master Meter wiring (see Omni drawing # 20900100 sheet 2 of 2)
14) AC Power receptacle with On/Off Switch
15) 3A DC and 0.5A AC Fuse holders
2 TB-060327 Only Revs 20.74+ & 24.74+

Getting Started
Technical support is OmniCom Configuration Files
available at:
(281) 240-6161 The Omni Prover Computer must be loaded with a valid configuration file before use.
Configurations are loaded using the OmniCom configuration program provide with the
the WEB Page at: flow computer. A configuration file contains information such as the type of prover (bi-
www.omniflow.com directional pipe or master meter) being used, prover water draw information, and
or email to: transducer scaling ranges, etc. The configuration file also contains information about
techsupport@omniflow.com the flowmeter being calibrated: meter tag name, meter K-Factor, and other
identification information about the flowmeter that appears on the prove report.
Step 1 - Create Generic Configuration Files for Each Prover

When an Omni prover computer is used with more than one prover, you must create a
generic OmniCom configuration file for each prover that will be connected. Each
configuration file will contain specific information relating to the prover, i.e. prover type
(bi-directional or master meter), water draw volume, transmitter-scaling values etc.
Save these configuration files using descriptive filenames that clearly identify the target
prover. Sample files for each prover type (bi-direction pipe and master meter) are
included with the Suitcase Prover Computer.
Step 2 - Create a Configuration File for Each Flowmeter to be Calibrated

For each flowmeter that will be calibrated:
a) Create a unique configuration file in OmniCom by opening the appropriate
generic file for the prover to be used (created at step 1 above).
b) Make the configuration file flowmeter specific by adding the target flowmeter’s
information, i.e. meter tag, meter ID, meter size, and meter K-Factor etc. This
information appears on the printed prove report which is produced at the
completion of a prove sequence (meter calibration).
c) Save the edited file using the ‘Save As’ feature of OmniCom. Use a descriptive
name that clearly identifies the target flowmeter. The filename given to the
configuration file can also form the basis of the filename that will be used when
prove reports are stored to the PC’s hard disk. This will make organizing and
retrieving reports for a specific flowmeter easy.
Step 3 – Connect the Prover Computer to the Prover

Using the MS connector shells provided, make up cables to connect the prover
computer to the prover instrumentation, and also to the flow meter being calibrated.
Refer to Omni drawing 20900100 (sheet 2) for details of the connector pin
designations. Make the connections observing all appropriate safety standards and
regulations. The suitcase prover computer is not suitable for operation in hazardous
areas.
Step 4 – Transmit the Flowmeter Specific Configuration File to the Prover

Computer
Connect the PC’s serial port to the prover computer using the cable supplied. Using
OmniCom, open the appropriate flowmeter configuration file and establish a
‘Connection’ to the Prover Computer. Transmit the configuration file to the Prover
Computer.
Step 5 – Operate the Prover Computer and Calibrate the Flowmeter

The prover sequence is initiated, and monitored as follows:
TB-060327 Only Revs 20.74+ & 24.74+ 3

Using the Control Panel Push Buttons to run the Prover

Momentarily pressing the ‘Prove Request’ button (6) on the control panel will
initiate a prove sequence. The lighted control panel buttons indicate the status
of the detector switches, launch command signals and prove sequence in
progress.
Using the Flow Computer Key Pad to run the Prover

a) Press ‘Program’ ‘Prove’ ‘Enter’
b) Scroll the cursor down to ‘Prove Meter ‘n’ and enter ‘1’ ‘Enter’
c) Enter a valid password if requested and press ‘Enter’. Tip: clearing the
Level 2 password in the ‘Password Maintenance’ menu will allow you
to bypass the password prompt by simply pressing the ‘Enter’ key
when requested for a password.
d) The flow computer will automatically return the LCD screen to the
Display mode and will show the meter counts and prove status as the
prove sequence progresses.
Using the OmniCom Software to run the Prover

a) Establish a connection to the Prover Computer by clicking the ‘Online’
button and double clicking on the ‘Direct 9600, Unit 1 – ID 1
selection. Note: The serial port on the Prover Computer defaults to
9600 baud,8,1,N Modbus ID 1
b) Select the ‘Operate’ mode.

c) In the left hand pane, select the ‘Control’, ‘Prover’ object. The screen
below displays:
4 TB-060327 Only Revs 20.74+ & 24.74+

d) Select the meter to prove in the drop down box .

Meter Run 1 = Test Meter, Meter Run 4 = Master Meter
e) To start a prove click on the button.
Step 6 - Printing and Saving the Flowmeter Calibration Prove Report

Perform the flowmeter calibration as described above. If a printer is connected to the
suitcase prover computer a Prove Report will print automatically after the prove
sequence completes. This Prove Report is also saved in the prover computer’s
historical storage buffer in. A maximum of eight prove reports can be stored in the
historical storage buffer before the oldest prove report is overwritten by the latest
report. To avoid overwriting valuable prove reports you must retrieve and save these
stored reports using OmniCom.
a) Select the ‘Operate’ mode.

b) In the left hand pane, select the ‘Historical Reports’, ‘Prove’ and then
select a prove report to retrieve from the prover computer. First is the
most recent report added, eighth is the oldest report. OmniCom will
automatically retrieve and display the selected prove report as shown
below
c) From this screen, you can choose to print the selected report to any
printer, local or network, accessible to the PC running OmniCom.
TB-060327 Only Revs 20.74+ & 24.74+ 5

Getting Tech Support - Step 7 – Saving the Report

available at: Use the button to save the selected report to disk. The path used to store
(281) 240-6161 the selected report will depend upon which disk the running copy of OmniCom is
Email should be sent via installed on (local or network). If you accepted the default options when Omni was
the WEB Page at: installed your prove reports will be stored on your local C: drive in one of two places
www.omniflow.com
or email to: depending upon the file naming convention selected when you clicked the
techsupport@omniflow.com button. Filenames with .p01 through .p08 extensions will be saved in
C:\OmniFlow\OmniCom\Reports. Filenames with .txt extensions will be saved in
C:\OmniFlow\OmniCom\Reports\Archive.
Filenames Compatible to those Created by DOS

OmniCom
Some users have legacy software applications which expect stored reports to have
filenames and extensions as created by previous versions of OmniCom running in a
DOS environment. These filenames have extensions of .p01 through .p08 and are
limited to eight character filenames. OmniCom provides filenames that are ‘Computer
ID’ based or configuration filename based.
Descriptive Filenames Created for use with

Windows OS
Microsoft Windows applications can use long filenames that allow for descriptive
filenames. These filenames have extensions of .txt OmniCom provides filenames that
are ‘Computer ID’ based or configuration filename based.
6 TB-060327 Only Revs 20.74+ & 24.74+

Date: 21 Apr 2006 Author(s): IP TB-060401
Communicating with SICK Ultrasonic Gas

Flowmeter Model Flowsic 600
Communicating with
SICK Ultrasonic Gas
Contents
Flowmeter Model
Flowsic 600
Scope .......................................................................................................1
This technical bulletin Abstract ...................................................................................................1
contained in the OMNI User
Flowsic 600 Ultrasonic Flowmeter Theory of Operation....................2
Manual, applicable to OMNI Flow Computer Logic...................................................................2
Revisions
23.74.20+/27.74.19+ Modbus Communication ........................................................................4
Note: OMNI firmware Wiring Installation...................................................................................5
23.74.20+ and 27.74.20+
support the SICK FLowsic OMNI Combo Module Terminal Assignments.................................................5
600 UFM with hardware
version 1.0 or 2.0 (i.e., one
Flowsic 600 Terminal Assignments ..................................................................8
serial port or two serial Flowsic 600 UFM Configuration Options Explained........................................9
ports respectively on the
UFM), whereas 27.74.19 Forward & Reverse Flow Signals ...................................................................11
supports UFM hardware Forward & Reverse Flow with Dual Pulse Fidelity Checking ........................12
version 1.0 only.
OMNI Flow Computer Configuration...................................................13
The SICK Flowsic 600
ultrasonic flowmeter Miscellaneous Configuration Meter Run Settings ..........................................13
measures gas flow by using
the Time Travel method of OMNI Flow Computer Database Addresses & Index Numbers ........16
acoustic pulses. This
device communicates with
OMNI Flow Computer User Displays...................................................21
OMNI flow computers via SV Module Serial Communications Port ........................................................21
OMNI’s ‘SV’ process I/O
combo module using a Meter Run Data ...............................................................................................24
proprietary protocol. To use
the scaled pulse output of
Scope
the SICK Flowsic 600, the
flow computer must have at
least an ‘A’, ‘B’ or ‘E’ combo
module installed.
This technical bulletin applies to firmware revisions 23.74.20+ and 27.74.19+ of
Getting Tech Support OMNI 6000/OMNI 3000 flow computers, for gas flow metering systems.
available at:
Phone: (281) 240-6161
Fax: (281) 240-6162
Abstract
Technical information is The SICK Flowsic 600 ultrasonic flowmeter determines the linear gas velocity
through the meter tube by using multiple acoustic pulse paths. The flowmeter
www.omniflow.com or send
email to: analyzes these paths employing the delta time travel measurement method. The
TB-060401 23.74.20+/27.74.19+ 1
OMNI flow computer either totalizes the flowmeter pulse input signal or
determines the flowrate from the serial port data received from the flowmeter.
Flowsic 600 Ultrasonic Flowmeter

Theory of Operation
SICK’s ultrasonic gas flow-metering technology incorporates multiple pairs of
transducers into a smart digital inferential instrumentation device. This device
is installed into a gas pipeline system to measure gas flow. Each pair of
Up to four pairs of transducers are positioned across the meter so that the path
upstream relative to the other. Pulses emitted by the downstream transducer are
slowed down by the velocity of the gas. With flow the pulse takes longer to
travel to the upstream transducer than with no flow. Pulses emitted by the
upstream transducer are aided by the velocity of the gas. With flow the pulse
takes less time to travel to the downstream transducer. Ultrasonic flowmeters
such as the Flowsic 600, that apply delta time methodology, measure these two
travel times to determine both the linear gas velocity and the speed of sound in
the gas. The flowmeter can measure velocity for bi-directional forward/reverse)
flow.

The OMNI flow computer can determine the actual flow rate from data received
either serially from the Flowsic 600 flowmeter, or from a live pulse frequency
signal input if one has been connected, assigned, and configured. In this
application, Modbus serial communication can be configured as the primary
measurement source with the pulse frequency configured as the backup
measurement source or vice versa to determine the actual flow rate. The OMNI
flow computer can also be configured to use only the Modbus serial
communication link with no pulse frequency input. When Modbus
communications are available the flow computer transmits flowing temperature
and pressure to the flowmeter to enable it to correct spool dimensions.
The OMNI retrieves the accumulated volume from the flowmeter. The flow
computer obtains a calculated volume increment by subtracting the new
accumulated volume from the previous accumulated volume it retrieved. The
flowmeter updates its totalizers on a regular interval depending upon flowing
conditions and configuration settings. Updating the OMNI totalizers on this
same period would result in somewhat erratic totalizers and sampler pulse
The OMNI provides a smooth totalizer update by monitoring the time interval
between Flowsic totalizer updates, and distributing the volume increment over a
matching time-period.
2 TB-060401 23.74.20+/27.74.19+
TB-060401 Communicating with SICK Ultrasonic Gas Flowmeter Model Flowsic 600
Start
SV Serial No Set SICK

Communications OK Communication
? Failed Alarm
Yes Velocity = Negative?

No
Yes
Clear SICK
Communication
Failed Alarm Configured as Configured as
Is
Reverse Flow In Forward Flow In
Omni?
No Omni?
No Pulse I/O
Assigned
Yes Yes No ?
Yes
Clear Flow Direction Set Flow Direction
Pulse Signal Primary? Mismatch Status Flag Mismatch Status Flag
(2n67) (2n67)
No
Yes Clear Pulse Signal Suspect
Alarm
Clear Pulse Suspect

Pulse I/O Assigned?
Alarm
No
Yes
Totalize Pulses for

Flow Comparison Flow Direction Digital I/O
Assigned?
No
Totalize Reverse
Configured as Flow
Forward Flow in from SV Link and
Yes
Omni? No Compare to Pulses
Flow
Yes Flow Direction Digital I/O
Indicates Forward Flow?
No
Totalize Forward Flow
from SV Link and Yes
Compare to Pulses Flow
Configured as Configured as
Reverse Flow In Forward Flow In
No Omni? No Omni?
Yes Yes
Is
Flow
Set Pulse Signal
Comparison
Suspect Alarm
within Limits No Set Flow Direction Clear Flow Direction
?
Mismatch Status Flag Mismatch Status Flag
Yes (2n67) (2n67)
Clear Pulse Signal

Suspect Alarm
Measurement Valid Digital

Is SV
I/O Assigned?
Communications Omni Flowrate
Primary Based on Pulses No
? No
Yes
Yes
Omni Flowrate
Based on SV Link
Measurement
Valid Digital Status OK ?
No
SV Link Indicates
Disable Totalizing Yes
Measurement Valid?
No
Yes
Totalize Flow Based on Pulse
Totalize Flow Based on SV Input Signal and in the direction
Link Serial Data configured in the Omni.
*(See Note below)
End
Figure 1. Flow computer logic flow diagram for the SICK Flowsic 600 ultrasonic gas
flowmeter. *Note: Totals will be applied in the Reverse or Forward direction depending
on status of the digital channel configured for flow direction. If a flow direction digital
channel is not configured, the flow will be applied in the direction specified in the OMNI
configuration for each meter run.
TB-060401 23.74.20+/27.74.19+ 3
In the event of a communication failure between the two devices, the OMNI
will not receive serial data. However, the Flowsic 600 may be fully operational
and continue to accumulate volume. In this case, if a pulse signal is available
from the flowmeter and the OMNI flow computer is configured to receive the
flow pulse signal as a backup, the flow computer will automatically continue to
necessary to match the Flowsic internal totalizer. The flow computer
automatically adjusts its totalizers to account for the small amount of flow that
takes place before it detects that a communication failure has occurred (i.e., the
OMNI does not immediately start totalizing using the Flowsic pulse train).
If a pulse signal from the Flowsic is not available (i.e., not assigned) and the
communication link fails, the flow computer immediately stops totalizing.
Once communication is reestablished, the OMNI will adjust its internal
totalizers to match the accumulated flow in the Flowsic since the last time it was
able to read from the Flowsic. In this case, the OMNI may have to add a
significant amount of flow to its totalizers, depending upon how much time the
communication link was inoperative.
In some instances, adjusting the flow computer’s totalizers may not be desirable
(e.g., if a flowmeter has been disconnected for a long period of time, or the
Flowsic electronics package has been replaced). For these cases, there are flow
computer configuration settings that specify the maximum time that a Flowsic
serial communication failure can exist, and still be compensated for by adjusting
the flow computer totalizers. By default, this maximum time is 15 minutes.
Modbus Communication
The Flowsic 600 connects to an external system using the Modbus ASCII
protocol via a serial line. This connection is a 2-wire RS-485 serial link.
Communications parameters are fixed in the OMNI at:
OMNI Flow Computer Fixed Communications

Parameters
Setting Value
Baud Rate 9600
Data Bits 8
Stop Bits 1
Parity None
Protocol Modbus ASCII
4 TB-060401 23.74.20+/27.74.19+
Serial Data Wiring Installation

Communications
The serial interface between There are several options for wiring a SICK Flowsic 600 ultrasonic meter to an
these devices is 2-wire RS- OMNI flow computer. The option to implement depends upon requirements of
Modbus ASCII protocol. the flow metering system. Contact SICK Maihak Technical Support (see
sidebar) for assistance with software/hardware configuration of the flowmeter.
Setting Up and Wiring
to OMNI Combo Always interconnect these devices via a 2-wire RS-485 serial interface from the
Modules Flowsic 600 to an OMNI SV combo module serial port. The OMNI uses the
In order to communicate Modbus ASCII protocol to determine the incremental flow from the data it
with SICK Flowsic 600 retrieves from the Flowsic 600 accumulators. The OMNI also transmits the fluid
ultrasonic flowmeters, the
OMNI flow computer must temperature and pressure to the flowmeter to allow the flowmeter to correct for
be equipped with at least dimensional changes of the measurement spool.
one SV combo module (68-
6203). For instructions on
jumper settings and other In addition to serial data, the OMNI can also receive live forward and/or reverse
process I/O combination flow pulse signals from the Flowsic 600. The Flowsic transmits pulse
module setup information,
please refer to Volume 1,
frequencies through wires typically connected to an OMNI combo module.
Chapter 2 of the OMNI Connecting two Flowsic 600 pulse output channels to the OMNI can provide
User Manual pulse fidelity and integrity checking. To perform pulse fidelity and integrity
checking, the OMNI must have an E combo module installed.
Getting SICK Maihak
Technical Support
OMNI Combo Module Terminal Assignments
SICK Maihak Technical
Support is available in
Germany or the U.S. The OMNI requires the SV combo module for serial communications plus
The contact information is
either an A or a B combo module if also connecting the flow pulse signal(s).
as follows: (Requires an E combo module instead of the A or B combo module if utilizing
the Pulse Fidelity and Integrity Checking feature with dual pulse trains).
In Germany:
The tables below specify the terminal assignments for each module type when
Phone: +49 35205 5240 connecting wires to the OMNI. The terminal block number (TBn) on the OMNI
Fax: +49 35205 52450 back panel for each combo module corresponds to the slot on the motherboard
Email: into which the module is plugged. Note: The highlighted areas indicate pinouts
Thomas.Horst@sick.de applicable to interfacing the OMNI to the SICK Flowsic 600 flowmeter.
In U.S.:
OMNI SV Combo Module Back Panel Terminal Assignments (TBn)
Phone: +1 (281) 436-5100
Fax: +1 (281) 436-5200
1 Port # 1 (3): RS-485 B Wire
Email: 2 Port # 1 (3): RS-485 A Wire
John.Hardin@sickmaihak.
com 3 Port # 2 (4): RS-485 B Wire
4 Port # 2 (4): RS-485 A Wire
also available at website: 6 Signal Return for 4-20mA Analog Outputs
www.sick-maihak.de 7 Analog Output # 5: 4-20mA
Note: Numbers in parenthesis “( )” refer to SV module 2 if installed.
TB-060401 23.74.20+/27.74.19+ 5
OMNI E Combo Module Back Panel Terminal Assignments (TBn)

5 Input Channel # 3: Flowmeter Pulses (independent channel or Pulse Train A for Pulse Fidelity)
6 Input Channel # 4: Flowmeter Pulses (independent channel or Pulse Train B for Pulse Fidelity)
Signal Return for Terminals 5, 6, 7, 8, 9, 11 & 12 (Internally connected to DC
10
power return
OMNI A Combo Module Back Panel Terminal Assignments (TBn)

10
return
Analog Output # 2: 4-20mA or RTD Excitation Current Source Output #2
12
(See JP12 Setting)
6 TB-060401 23.74.20+/27.74.19+
OMNI B Combo Module Back Panel Terminal Assignments (TBn)

7 Input Channel # 4: Densitometer Pulses
10
return
12 RTD Excitation Current Source Output #2 (See JP12 Setting)
TB-060401 23.74.20+/27.74.19+ 7
Flowsic 600 Terminal Assignments

There are two hardware variants of the Flowsic 600 flowmeter that can be
selected using hardware jumper settings. Consult the Flowsic manual for
specific details on procedures to change the related jumpers. Note: The
hardware “variant” is not the same as the hardware “version”referenced in
the sidebar on page 1 of this bulletin (i.e., both hardware “versions” 1.0 and
2.0 have user selectable Hardware “variant” 1 or 2. Variant 2 provides a
second serial port.
The hardware variant can be selected via the Jumper 2 setting on what is known
as the Back Board on the flowmeter. In addition to selecting the hardware
variant, the same jumper can be used to specify if the outputs are to be Open
Collector (Active) or NAMUR (Passive) signals. Use the Open Collector option
when connecting to the OMNI flow computer.
The “variant” or specific assignments of the digital outputs DO 1 through DO 3

can be software configured with the help of the MEPAFLOW 600 PC-Based
program used to configure the flowmeter.
The highlighted areas in the two tables that follow indicate how the flowmeter
should be configured for interfacing to the OMNI when using either variant.
Hardware Variant 1 (without current output)

Output Terminal Assignment
Digital Out 0 31+, 32- Actual Volume (frequency signal), inverted to Digital Output 1, constant
“open” with fault.
Serial Interface 33+, 34- RS-485 2-Wire
Digital Out 1 51+, 52- Actual Volume (frequency signal)
Digital Out 2 Data Invalid or Config Mode = High signal
41+, 42-
Data Valid or Measurement Mode = Low signal
Digital Out 3 81+, 82- Direction of Flow
Forward Flow = High signal, Reverse Flow = Low signal
Hardware Variant 2 (with current output)

Output Terminal Assignment
Serial Interface 33+, 34- RS-485 2-Wire Port 1
Digital Out 2 41+, 42- Data Invalid = High signal (Config Mode) and
or Data Valid = Low signal (Measurement Mode)
Serial Interface RS-485 2-Wire Port 2
Digital Out 3 81+, 82- Direction of Flow
Forward Flow = High signal, Reverse Flow = Low
signal
8 TB-060401 23.74.20+/27.74.19+
Flowsic 600 UFM Configuration Options Explained

Following are the software and hardware settings available in the SICK Maihak
Flowsic 600 UFM when connecting to the OMNI flow computer.
Option 1)
Frequency outputs D0, D1 (51/52-31/32) setting = Flow (DO1) + Direction

(DO0)
Either Normally Open (D0+D1) or Normally Closed (D0+D1)
Hardware jumper set to DO0 = frequency
This configuration creates the same frequency on terminals 31/32 and 51/52 but
the phase shift is dependent on flow direction.
Dual pulse trains are provided simultaneously in both the forward and reverse
flow directions for pulse fidelity and integrity checking. The phase shift in the
forward direction is 90 degrees and 180 degrees in the reverse direction. It is
possible to use this configuration with the OMNI flow computer if configuring
two separate meter runs in the flow computer with each meter run representing
different flow directions, and with each meter run assigned different flow pulse
input channels.
Option 2)
Frequency output D0, D1 (51/52-31/32) setting = Flow (DO1) + Invalid (DO0)
Either Normally Open (D0+D1) or Normally Closed (D0+D1)
This configuration provides dual pulse trains for purposes of dual pulse fidelity
and integrity checking with the signals 180 degrees out of phase. Both signals
are normally active simultaneously in either the forward or reverse flow
directions. If there exists a data invalid situation in the flowmeter, terminals
31/32 will not output a frequency.
Note: An internal Data Invalid situation or switching the meter to

"Configuration" mode will cause a Data Invalid signal to be output.
TB-060401 23.74.20+/27.74.19+ 9
Option 3)
Frequency output D0,D1 (31/32-51/52) setting = Flow FW(DO1) + RW(DO0)
Either Normally Open(D0+D1) or Normally Closed (D0+D1)
This configuration also provides dual pulse trains but not for pulse fidelity and
integrity checking. The signals are mutually exclusive of one another - while
one signal is on, the other is off. The DO1 signal is used to indicate forward
flow and the DO0 signal is used to indicate reverse flow.
Dependent on the flow direction, the meter outputs a frequency only on

terminals 51/52 for forward flow or the meter outputs a frequency only on
terminals 31/32 for reverse flow.
Option 4)
Frequency output D0,D1 (31/32-51/52) setting = Flow FW(DO1) + status

output(DO0)
Either Normally Open(D0+D1) or Normally Closed (D0+D1)
This configuration provides only one pulse train on terminals 51/52. Terminals
31/32 can be configured for status output signals (i.e. Data Invalid, Warning,
Flow Direction, Check Request).
10 TB-060401 23.74.20+/27.74.19+

Shown below is a typical wiring installation between the SICK Flowsic 600 and
an OMNI 6000 for serial data and both forward and reverse flow signals. In this
example, assume that the OMNI 6000 has an A or B Combo module plugged
into slot TB5, and an SV module in slot TB6.
SICK Flowsic 600 Field

Connection Term inal OMNI A Com bo Module Term inals
(TB5)
Freq B+ 31 1
Freq B- 32 2
RS485 + 33 3
RS485 - 34 4
Pulse In
Freq A+ 51 5
Return 3rd Input Channel
Freq A- 52 6 of A or B Com bo
Pulse In
Mode+ 41 7 OR
Return 4th Input Channel
Mode- 42 8 of A Com bo
Flow Dir+ 81 9
Flow Dir- 82 10
11
12
OMNI Digital I/O

OMNI SV Com bo Module Term inals
Module Term inals (TB1)
(TB6)
1 Digital In 1 1 RS-485 - (B)
Port #1 **
2 Digital In 2 2 RS-485 +(A)
3 3 RS-485 - (B)
Port #2 **
4 4 RS-485 +(A)
5 5
6 All Pull-up Resistors 6
Approxim ately 2KOhm
7 7
8 8
9 9
10 10
+ + + + - - - -
11 11
OMNI TB11 (- signal internally tied to
12 pin 10 of Com bo m odules)
12
Figure 2. Example of wiring a Flowsic 600 ultrasonic flowmeter to an

OMNI 6000 flow computer with connections for serial data and live forward and
reverse flow signals (without pulse fidelity and Integrity checking).
**Ports 1 or 2 of the SV1 combo module or ports 3 or 4 of the SV2 combo
module can be utilized.
TB-060401 23.74.20+/27.74.19+ 11
Forward & Reverse Flow with Dual Pulse Fidelity Checking

Shown below is a typical wiring installation between the SICK Flowsic 600 and
an OMNI 6000 for serial data and forward and/or Reverse flow signals, with
connections for pulse fidelity and integrity checking. In this example, assume
that the OMNI 6000 has an E module plugged into slot TB5, and an SV module
in slot TB6.
SICK Flowsic 600 Field

Connection Terminal OMNI E Com bo Module Term inals
(TB5)
Freq B+ 31 1
Freq B- 32 2
RS485 + 33 3
RS485 - 34 4
Pulse A+ In
Freq A+ 51 5 3rd Input Channel
Pulse B+ In
Freq A- 52 6 4th Input Channel
Mode+ 41 7
Mode- 42 8
Flow Dir+ 81 9
Return
Flow Dir- 82 10
11
12
OMNI Digital I/O

OMNI SV Com bo Module Term inals
Module Term inals (TB1)
(TB6)
1 Digital In 1 1 RS-485 - (B)
Port #1 **
2 Digital In 2 2 RS-485 +(A)
3 3 RS-485 - (B)
Port #2 **
4 4 RS-485 +(A)
5 5
6 All Resistors 6
7 Approxim ately 2KOhm 7
8 8
9 9
10 10
+ + + + - - - -
11 11
OMNI TB11 (- signal internally tied
12 to pin 10 of Com bo m odules)
12
Figure 3. Example of wiring a Flowsic 600 ultrasonic flowmeter to an

OMNI 6000 flow computer with connections for serial data,
live forward & reverse flow signal, and pulse fidelity and
integrity checking.
**Ports 1 or 2 of the SV1 Combo module or ports 3 or 4 of
the SV2 Combo module can be utilized.
12 TB-060401 23.74.20+/27.74.19+
OMNI Flow Computer Configuration

Use either the flow computer’s front panel keypad or the OmniCom for Windows PC-
based software program to enter configuration settings unique to the SICK Flowsic
600 flowmeter. The configuration settings that are specific to the Flowsic 600 are
under Miscellaneous Setup, Configure Meter Run menu and the Meter Run Setup
menu if accessing the settings from the keypad.
Enter the miscellaneous configuration meter run settings first and then proceed to the
meter run setup entries (see Chapter 2 ‘Flow Computer Configuration’ in Volume
3 of the OMNI User Manual, and the technical bulletin TB-960701 ‘Overview of
OmniCom Configuration PC Software’).

Flowsic 600 ultrasonic gas flowmeter:
Select Flowmeter Device Type – For each meter run, enter [10] to select
the SICK Ultrasonic flowmeter as the device type.
Select SV Module Port – The OMNI flow computer can accept two SV
combo modules (these are not the same as regular serial modules). With one SV
module, two SV ports are available, and with two SV modules, four ports are
available. For each ultrasonic meter run, enter the SV port number (1 to 4) to
which the SV module’s RS-485 2-wire serial interface input from the Flowsic 600
flowmeter is wired to the OMNI.
SICK Address – This is the address ID of the SICK ultrasonic flowmeter

communications port.
SICK Retry # – This is the number of SV serial port communications

consecutive retries the OMNI will attempt with the flowmeter when the flowmeter
does not respond before the OMNI raises a communications fail alarm.
Delay Seconds – This is the number of seconds the OMNI should wait for a
response from the flowmeter before the OMNI attempts a communications retry.
The flowmeter response time can vary depending on the tasks being performed at
the time data is requested. If the specified number of retries has been exhausted
without a response from the flowmeter, the flow computer will raise a
communications failure alarm. (Recommended value is 2 seconds)
Flow I/O Point – Enter the flow pulse input channel number of the flow
computer where the ultrasonic flowmeter pulse signal is wired to. Assign
flowmeter pulse signals only to Input Channels #3 and #4 of A or E combo
modules, or input channel #3 of a B combo module.
Dual Pulse? (Y/N) – A “Y” indicates to the flow computer there are two
pulse trains coming from the flowmeter and they should be compared using the
Pulse Fidelity and Integrity Checking feature. The channel assigned in the
TB-060401 23.74.20+/27.74.19+ 13
previous setting will be considered the “A” pulse train and the channel immediately
following will be considered the “B” pulse train. Ensure the pulse train signals are wired
accordingly. Note: Use of this feature requires an E-Combo module.
Select Flow Direction (F/R) – Flowsic 600 flowmeters allow for bi-
directional flow measurement. Set up the flow computer to totalize either the forward or
the reverse flow on any meter run with an ultrasonic flowmeter. Note: If you would like
the OMNI flow computer to measure flow in both directions, you should set up two meter
runs in the OMNI, one configured for forward flow and the other configured for reverse
flow.
Flow Direction Digital Input # – Specify which digital input channel in

the OMNI will be receiving the signal indicative of the flow direction. This input signal is
used for purposes of flow pulses totalizing only and not for totalizing with respect to the
serial port data.
The OMNI will use this status signal if there is a failover from the serial communications
link to the pulses OR if the pulses are specified as the primary means of measurement.
A high output digital signal from the flowmeter indicates the flow is in the forward
direction whereas a low signal indicates the flow is in the reverse direction.
If the signal indicates a direction that is different than what is configured for the Select
Flow Direction setting, the OMNI will not totalize flow for the respective meter run and
will set flag 2n67 to indicate a flow direction mismatch.
Measurement Status Digital Input # – This input signal is used for

purposes of flow pulses totalizing only and not for totalizing with respect to the serial port
data. The OMNI will use this status signal if there is a failover from the serial
communications link to the pulses OR if the pulses are specified as the primary means of
measurement.
A high output digital signal from the flowmeter indicates the flowmeter is in the
“configuration” mode whereas a low signal indicates the flowmeter is in the
“measurement” mode. Specify which digital input channel in the OMNI will be receiving
the signal indicative of the measurement status.
Note: When the flowmeter indicates it is in the configuration mode, the OMNI will not
totalize.
Primary Flow – This setting instructs the OMNI flow computer to use
either the pulse input channel or the SV serial communications data as the primary means
of calculating flow. Options are:
0 = Select Serial Data as primary flow. This means that the SV serial communications
data will be the primary and the pulse input channel, if assigned, will be used as a backup
means of flow calculations by the flow computer.
1 = Select Pulse Input as primary flow. This means that the flow pulses received from the
flowmeter will be the primary and the SV serial communications data will be used as a
backup means of flow calculations by the flow computer.
14 TB-060401 23.74.20+/27.74.19+
Defining ‘Velocity of Meter Run Setup Entries

Sound’
The ‘velocity of sound’
The following meter run setup entries in the OMNI flow computer are available
(VOS) refers to the amount for the Flowsic 600 ultrasonic flowmeter:
of time it takes an acoustic
pulse to travel along the gas
ultrasonic paths. The VOS Velocity of Sound (VOS) Deviation Percent from Average – In instances
will vary depending upon where the serial data is being used as the means of totalizing, the flow
gas type and line computer can verify that the average VOS calculated for all paths conforms
conditions.
to the VOS of each individual path. This entry is the maximum percent that
any one path VOS varies from the average VOS of all the paths. The flow
computer will raise an alarm if this percentage limit is exceeded.
AGA 10 Velocity of Sound (VOS) Deviation Percent from Average –

Only valid if AGA 10 is enabled in the OMNI flow computer. The flow
computer can verify that the average VOS calculated for all Flowsic 600
paths conforms to the AGA 10 VOS calculated by the OMNI flow
computer. The flow computer will raise an alarm if this percentage limit is
exceeded.
Flow Minutes – Only valid if a flow pulses I/O point is assigned. The time
interval can be set for comparing the flow pulses input flow with the SV
communications serial link flow. If the flow deviation exceeds the Flow
Deviation Percent setting (see next setting) when this comparison is made,
the OMNI will switch from the primary (flow pulses) to the backup source
(SV serial link) for calculating flow. (Note: It is recommended a minimum
of 60 minutes be specified for this setting due to the fluctuating flow pulse
frequency.)
Maximum Flow Deviation Percent ⎯ Only valid if a flow pulses I/O

point is assigned - this is the allowable percent of deviation between the
calculated flow from the pulse input channel compared to the Flowsic 600
flow data received via the OMNI SV serial port. The OMNI raises the
pulse suspect alarm if the flow deviation percentage exceeds this limit and
switches to the SV serial port as the primary means of totalizing. (Note: See
the previous setting relating to Flow Minutes).
Maximum Meter Downtime ⎯ Enter the maximum allowable flowmeter

downtime in minutes. If communication downtime between the OMNI and
the Flowsic 600 is greater than this value, the OMNI will not adjust its
internal totalizers to match the Flowsic 600 totalizer increment when serial
communications is reestablished. Depending upon how much time the
communication link and pulses were inoperative and the amount of flow
that occurred during this downtime, when communications is reestablished
within the time specified in this setting, the OMNI may have to add a
significant amount of flow to its totalizers. (Default = 15 minutes). (Note:
If you do not wish the OMNI to compensate for any flowmeter downtime,
specify a value of 0 for this setting)
TB-060401 23.74.20+/27.74.19+ 15
OMNI Flow Computer Database

Addresses & Index Numbers
The following tables list the Modbus database addresses assigned within OMNI
firmware to the Flowsic 600 ultrasonic metering feature. These tables
categorize data type.
Database Address
Description For Meter Run Number
1 2 3 4
Loss of communication Alarm 2154 2254 2354 2454
Pulse Suspect Alarm 2155 2255 2355 2455
Flow rate deviation Alarm 2156 2256 2356 2456
Meter in Configuration mode 2157 2257 2357 2457
Meter in Reduced Accuracy 2158 2258 2358 2458
mode
Path 1 Error 2159 2259 2359 2459
Path 2 Error 2160 2260 2360 2460
Path 3 Error 2161 2261 2361 2461
Path 4 Error 2162 2262 2362 2462
SICK EPROM Error 2163 2263 2363 2463
I/O Parameter Error 2164 2264 2364 2464
Warn I/O Range 2165 2265 2365 2465
DSP – fault 2166 2266 2366 2466
Flow Direction Mismatch 2167 2267 2367 2467
DSP Parameter Error 2168 2268 2368 2468
Path 1 AGC Deviation Alarm 2169 2269 2369 2469
Path 1 SOS Deviation Warning 2173 2273 2373 2473
Path 1 - VOS Deviation Alarm 2181 2281 2381 2481
16 TB-060401 23.74.20+/27.74.19+

Database Address
1 2 3 4
Flow Direction Configuration 3155 3255 3355 3455
(0=forward,1=reverse)
System Control Register 3171 3271 3371 3471
System Status 3172 3272 3372 3472
Numbers of Paths 3173 3273 3373 3473
Flow Meter Type 3174 3274 3374 3474
Valid Samples Path 1 3175 3275 3375 3475
AGC Level Receiver 1A 3180 3280 3380 3480
AGC Level Receiver 1B 3181 3281 3381 3481
VBatt Level 3188 3288 3388 3488
Frequency Current 3189 3289 3389 3489

Database Address
1 2 3 4
Flowsic SN Device 15524 15624 15724 15824
Flowsic Software Version 15525 15625 15725 15825
Flowsic SN Analog 15526 15626 15726 15826
Flowsic Constants CRC 15527 15627 15727 15827
Flowsic Program CRC 15528 15628 15728 15828
Flowic Parameter CRC 15529 15629 15729 15829
Flowsic Forward Volume 15530 15630 15730 15830
Flowsic Fwd Volume Error 15531 15631 15731 15831
Flowsic Reverse Volume 15532 15632 15732 15832
Flowsic Rev Volume Error 15533 15633 15733 15833
Flowsic Counter Resolution 15534 15634 15734 15834
Flowsic Response Delay 15535 15635 15735 15835
TB-060401 23.74.20+/27.74.19+ 17

1 2 3 4 1 2 3 4
Serial Gross flow during Flow 17141 17151 17161 17171 Path 1 Velocity of Sound 17527 17627 17727 17827
Minutes period
Pulses Gross flow during Flow 17142 17152 17162 17172 Path 2 Velocity of Sound 17528 17628 17728 17828
Minutes period
Calculated Flow Dev % 17143 17153 17163 17173 Path 3 Velocity of Sound 17529 17629 17729 17829
Max flow dev (%) allowed 17513 17613 17713 17813 Path 4 Velocity of Sound 17530 17630 17730 17830
Total increment from serial 17213 17217 17221 17225 Path 1 Gas Velocity 17533 17633 17733 17833
link (2nd to last read)
Total increment from serial 17214 17218 17222 17226 Path 2 Gas Velocity 17534 17634 17734 17834
link (last read)
Total from pulse input 17215 17219 17223 17227 Path 3 Gas Velocity 17535 17635 17735 17835
Dev % between serial & pulse 17216 17220 17224 17228 Path 4 Gas Velocity 17536 17636 17736 17836
*Max VOS dev (%) allowed 17516 17616 17716 17816 Volume Flowrate – Line 17525 17625 17725 17825
Avg VOS – All Paths 17521 17621 17721 17821 Volume Flowrate - Base 17526 17626 17726 17826
Avg Gas Velocity – All Paths 17522 17622 17722 17822 **Max Allowed VOS Dev % 17518 17618 17718 17818
(OMNI v23 firmware)
SICK Press – Absolute BarA 17523 17623 17723 17823 **Max Allowed VOS Dev % 17599 17699 17799 17899
(OMNI v27 firmware)
SICK Temperature - Kelvin 17524 17624 17724 17824 ***OMNI Calculated AGA10 18524 18624 18724 18824
VOS in m/s (OMNI v23 & 27
firmware)
SICK K-Factor 17538 17638 17738 17838 ***OMNI Calculated AGA10 18532 18632 18732 18832
VOS in ft/s (OMNI v23 & 27
firmware)
Temperature 7105 7205 7305 7405
Pressure 7106 7206 7306 7406
* The VOS of each individual path is compared against the composite VOS in the SICK Flowsic 600 and an
alarm is raised by the OMNI if this percentage limit is exceeded.
** Applicable only if AGA 10 is enabled in the OMNI. This is the result of the comparison between the SICK
Flowsic 600 composite VOS versus the OMNI calculated AGA 10 VOS. The OMNI raises an alarm if this
percentage limit is exceeded.
*** Applicable only if AGA 10 is enabled in the OMNI.
18 TB-060401 23.74.20+/27.74.19+

Description for Meter Run Number for Meter Run Number
1 2 3 4 1 2 3 4
Valid Sample Path 1 17539 17639 17739 17839 Valid Sample Path 1 17569 17669 17769 17869
AGC Level Receiver 1A 17543 17643 17743 17843 AGC Level Receiver 1A 17574 17674 17774 17874
AGC Level Receiver 1B 17544 17644 17744 17844 AGC Level Receiver 1B 17575 17675 17775 17875
Path 1 Gas velocity 17553 17653 17753 17853 Path 1 Gas velocity 17584 17684 17784 17884
Path 1 Velocity of Sound 17561 17661 17761 17861 Path 1 Velocity of Sound 17592 17692 17792 17892
TB-060401 23.74.20+/27.74.19+ 19

1 2 3 4 1 2 3 4
Flow pulse I/O point # 13001 13014 13027 13040 Flow Direction Digital Input # 3162 3262 3362 3462
Flowmeter device type 3108 3208 3308 3408 Meter Mode Digital Input # 3163 3263 3363 3463
SV module port # assigned 3153 3253 3353 3453 0=Measurement 1=Config
Flowsic 600 Modbus ID 3154 3254 3354 3454 Delay Retry Seconds 13445 13446 13447 13448
SICK Retry # 3156 3256 3356 3456
Primary Flow 3157 3257 3357 3457
(0=Serial, 1=Pulses)

1 2 3 4 1 2 3 4
Meter maximum downtime 3116 3216 3316 3416 *VOS deviation (%) 17516 17616 17716 17816
(minutes) **Max Allowed VOS Dev % 17518 17618 17718 17818
(OMNI v23 firmware)
Flow Compare Interval Time – 3135 3235 3335 3435 **Max Allowed VOS Dev % 17599 17699 17799 17899
(minutes) (OMNI v27 firmware)
Serial to Pulses flow compared
Maximum flow deviation (%) 17513 17613 17713 17813 K-factor from SICK UFM 17538 17638 17738 17838
* The VOS of each individual path is compared against the composite VOS in the SICK Flowsic 600 and an alarm is raised by
the OMNI if this percentage limit is exceeded.
**Applicable only if AGA10 is enabled in the OMNI. This is the result of the comparison between the SICK Flowsic 600
Composite VOS versus the OMNI calculated AGA10 VOS. The OMNI raises an alarm if this percentage limit is exceeded.
20 TB-060401 23.74.20+/27.74.19+
OMNI Flow Computer User Displays

interface from the Flowsic 600 flowmeter. To view this data, press [Setup] [n]
[Display] on the OMNI front panel keypad (where “n” equals the SV port
number 1 to 4, you want to display), when in the Display Mode.
The following data displays assume that when you have a version 23 firmware
OMNI, the Flowsic 600 flowmeter will be configured for Imperial Units and
when you have a version 27 firmware OMNI, the Flowsic 600 flowmeter will
be configured for Metric Units:
OMNI Version 23 Firmware OMNI Version 27 Firmware
SV Portn FLOWSIC 600 SV Portn FLOWSIC 600
Meter Type xxx Meter Type xxx
System Reg xxxx System Reg xxxx
SystemStatus xxxxx SystemStatus xxxxx
Path1 Status x Path1 Status x
Path1 Sample x Path1 Sample x
Path 1A AGC xx Path 1A AGC xx
Path 1B AGC xx Path 1B AGC xx
TB-060401 23.74.20+/27.74.19+ 21
Continued (version 23) Continued (version 27)
VBatt Level xxxxx VBatt Level xxxxx
Freq Current xxxxx Freq Current xxxxx
SN Device xxx SN Device xxx
SW Version xxxx SW Version xxxx
SN Analog xxx SN Analog xxx
Constants CRC xxxx Constants CRC xxxx
Program CRC xxxx Program CRC xxxx
Parameter CRC xxxx Parameter CRC xxxx
Fwd Vol xxxxxx.x Fwd Vol xxxxxx.x
F.VolErr xxxx.x F.VolErr xxxx.x
Rev Vol xxx.x Rev Vol xxx.x
R.VolErr .x R.VolErr .x
CtResolution xxx CtResolution xxx
ResponseDely x ResponseDely x
FwRateLn xxxx.xxx FwRateLn xxxx.xxx
FwRateBs .xxx FwRateBs .xxx
Avg.VOS xxxx.xxxxx Avg.VOS xxxx.xxxxx
Avg Vel xx.xxxxx Avg Vel xx.xxxxx
VOS P1 xxxx.xxxxx VOS P1 xxxx.xxxxx
Vel P1 xx.xxxxx Vel P1 xx.xxxxx
SNR 1A xx.xxx SNR 1A xx.xxx
22 TB-060401 23.74.20+/27.74.19+
Continued (version 23) Continued (version 27)
SNR 1B xx.xxx SNR 1B xx.xxx
Temp K xxx.xx Temp K xxx.xx
P. (abs) xxx.xxx P. (abs) xxx.xxx
RealGasFc x.xxxxxx RealGasFc x.xxxxxx
Temp Base K xxx.xxx Temp Base K xxx.xxx
P.Base xx.xxxxx P.Base xx.xxxxx
RealFcBas x.xxxxxx RealFcBas x.xxxxxx
MFp/unit xxx.xxx MFp/unit xxx.xxx
LowCutOff xx.xxx LowCutOff xx.xxx
AdjFcFwd x.xxxxxx AdjFcFwd x.xxxxxx
AdjFcRev x.xxxxxx AdjFcRev x.xxxxxx
ZeroOffset .xxxx ZeroOffset .xxxx
Temp Fix xxx.xxx Temp Fix xxx.xxx
PressureFix xx.xxx PressureFix xx.xxx
CompressFix x.xxxx CompressFix x.xxxx
TB-060401 23.74.20+/27.74.19+ 23
Meter Run Data

To view the meter run data on the flow computer LCD display, press [Meter]
[n] [Display] on the OMNI front panel keypad (where “n” equals the meter run
number, 1 to 4, you want to display), when in the Display Mode. The following
data will display:
OMNI Version 23 Firmware OMNI Version 27 Firmware
METER #n FLOWSIC 600 METER #n FLOWSIC 600
VEL ft/s xx.xxxxx VEL m/s xx.xxxxx
KF P/ft3 xxx.xxx KF P/m3 xxx.xxx
Flowft3h xxxx.xx FlowM3/h xxxx.xx
VOS ft/s xxxx.xxxxx VOS m/s xxxx.xxxxx
Fwd Vol xxxxxx.x Fwd Vol xxxxxx.x
Rev Vol xxx.x Rev Vol xxx.x
P. psia xxx.xx P. bara xxx.xx
T. Deg.K xxx.xx T. Deg.K xxx.xx
GasVelP1 xx.xxxxx GasVelP1 xx.xxxxx
24 TB-060401 23.74.20+/27.74.19+
Page Intentionally Left Blank
TB-060401 23.74.20+/27.74.19+ 25
Date: 04 19 06 Author(s): K.E. Version: TB-060419
O mni 3
Omni 000/ 6000 T
3000/6000 otalizer F
Totalizer unctions
Functions
Contents
Scope....................................................................................................... 1
supplements the information Abstract ................................................................................................... 1
Manual, applicable to all Basic Totalizer Function ........................................................................ 2
Omni flow computer
firmware revisions. Increments of Flow ........................................................................................... 2
Order of Calculation.......................................................................................... 3
Types of Totalizer ................................................................................... 4
Omni Technical support is
Flowrate versus Totalization ................................................................. 5
available at:
Phone: (281) 240-6161
Fax: (281) 240-6162
Scope
Technical information is This technical bulletin applies to all firmware revisions of Omni 3000/6000 flow
computers.
www.omniflow.com
Or send email to:
Abstract
This technical bulletin discusses the Totalization Functions of the Omni 3000,
and 6000 Flow Computer. This bulletin does not discuss the various ‘Fluid
Properties’ algorithms and procedures used by the flow computer to compensate
measured volumes and mass quantities to base or standard conditions.
Information about these algorithms and implementation procedures can be found
in standards documents published by industry standards organizations such as
the American Petroleum Institute (API), and the International Standards
Organization (ISO). Because of international copyright laws and space
limitations it is not possible or practical to include complete documentation on
these standards within the Omni manual. In some cases, excerpts of these
algorithms and procedures are contained in the Omni Flow Computer Manual,
Volume 3, Chapter 4 and 5, Flow Equations and Algorithms.
TB-060419 All Revisions 1

Basic Totalizer Function

The function of a totalizer is to continuously integrate all flow measured by the
flowmeter device. Totalizers within the flow computer are tamperproof and
stored in the flow computers memory as redundant long integer registers with
checksum security. Long integers are used because (unlike floating point
numbers) they can ‘exactly’ represent all whole numbers between 0 and
1,000,000,000. Sometimes the totalizers have inferred decimal resolution, i.e.
the value stored in the registers represents decimal fractions of a volume or mass
unit (tenths of barrels for example x.x bbls).
Increments of Flow
The flow computer monitors electrical signals from the flowmeter device and
calculates incremental flow every 500mS calculation cycle. Flowmeter signals
can be pulses, where every pulse counted represents a specific volume (mass in
the case of a Coriolis flowmeter) or, analog current or voltage in the case of a
DP head device (orifice meter for example).
These 500 mS. increments of flow are calculated to high accuracy and are stored
as extended precision floating point numbers (17 decimal digits of precision).
The flow increments are integrated until they are large enough to be transferred
into the relevant integer totalizers. Any fractional amount (remainder) not
transferred into the totalizer is saved and added to the next calculation cycle’s
calculated flow increment.
Multiple flow increments are calculated for each flowmeter run, every
calculation cycle. These are: Gross volume increment, Net volume increment,
Mass increment, and Energy increment. Liquid applications do not totalize
energy but do require an S&W corrected Net increment.
Gross Volumes at flowing temperature and pressure
conditions
Net Equivalent volumes at base temperature and
pressure conditions
Mass Mass quantities
For Liquid applications only:
S&W corrected Net Equivalent volume at base temperature and
pressure with Sediment and Water removed
For Gas applications only:
Energy Energy quantities
2 TB-060419 All Revisions

TB-060419 Omni 3000/6000 Totalizer Functions
Order of Calculation
This technical bulletin Flow increments for a specific flowmeter run are related to one another and are
supplements the information calculated in a preset order. This depends upon the flowmeter technology being
Manual, applicable to all
used.
Omni flow computer
firmware revisions.
Flowmeters that produce volume based pulses (Turbine, PD meters, etc):
1. The Gross flow increment is calculated
Omni Technical support is 2. The Net flow increment is calculated based on the Gross flow
available at: increment and fluid specific correction factors
Phone: (281) 240-6161
If Liquid application:
Fax: (281) 240-6162
3. The S&W corrected Net increment is calculated by adjusting
available on our website at: the Net flow increment for S&W content
www.omniflow.com
4. The Mass flow increment is calculated based on either:
Or send email to:
techsupport@omniflow.com • the Gross flow increment and fluid density at flowing
temperature and pressure
Or
• the Net flow increment and fluid density at base
temperature and pressure
If Gas application:
5. The Energy flow increment is calculated based on either:
• the Net flow increment and heating value per Net
volume unit
Or
• the Mass flow increment and heating value per Mass
unit
Flowmeters that produce mass based pulses (Coriolis meters):

1. The Mass flow increment is calculated
2. The Net flow increment is calculated based on the Mass flow

increment and fluid density at base temperature and pressure
conditions

the Net flow increment for S&W content
4. The Gross flow increment is calculated based on the Mass flow

increment and density at flowing temperature and pressure

If Gas application:
5. The Energy flow increment calculated based on either:
• the Net flow increment and heating value per Net
volume unit
Or
• the Mass flow increment and heating value per Mass
unit
DP Head Devices whose flow calculation gives a mass flow result

(Orifice meters etc.):
1. The Mass flow increment is calculated
2. The Net flow increment is calculated based on the Mass flow

increment, and density at base temperature and pressure
conditions

the Net flow increment for S&W content
Types of Totalizer
The flow computer provides the following groups of totalizers:
Cumulative Totalizers These totalizers are never reset during
normal operations. They can be reset by
following a totalizer reset procedure and
entering the correct security password. They are
snapshot to provide opening and closing
readings that appear on batch and daily reports.
Batch Totalizers These totalizers represent a batch quantity
being delivered or received. They are
automatically captured for reporting purposes
and reset to zero when a batch end command is
received.
Daily Totalizers These totalizers represent the current daily
quantity delivered or received. They are
captured for reporting purposes and reset every
24 hours at the Day Start Hour specified.
4 TB-060419 All Revisions

TB-060419 Omni 3000/6000 Totalizer Functions

Flowrate versus Totalization
supplements the information The function of a totalizer is to accurately represent all flow which passed
Manual, applicable to all through the flowmeter device. The function of a flowrate indication is primarily
Omni flow computer operational, i.e. it is used for control purposes and should be easy to read on a
firmware revisions.
digital display. Flowrates calculated by the flow computer are not integrated to
provide totalizers.
Totalizers are based on the integration of many discrete flow increments that are
Omni Technical support is calculated by the flow computer every 500 mS. Flowrates are also calculated
available at:
using the same flow increments used to produce totalizers but they are usually
Phone: (281) 240-6161 digitally filtered to produce a smooth readout that is easy to read. Filtering is
Fax: (281) 240-6162 needed because the input data used to calculate each 500 mS. flow increment
Technical information is may be quite variable. A frequency of 49 Hz from a turbine meter for example,
available on our website at: would cause every other 500 mS. flow increment calculation to be based on
www.omniflow.com either 25 turbine meter pulses, or 24 turbine meter pulses, a 4% bobble which
Or send email to: would be very difficult to read on a digital readout.

Date: 14 August 2006 Author(s): I. P. / K. E. TB-060801
Understanding OMNI Flow Computer Time

Synchronization
User Manual Reference Contents

This technical bulletin is
applicable to all OMNI flow Scope .......................................................................................................1
computer firmware versions
and supplements the
Abstract ...................................................................................................1
information contained in the Ethernet-to-Serial Port Terminal Servers .............................................3
OMNI User Manuals.
Background .............................................................................................3
Example ...................................................................................................4
Digital I/O Assignment .....................................................................................5
Boolean Statements ...........................................................................................6
Variable Statements...........................................................................................7
Programmable Statements Analysis.....................................................8
Scope
This technical bulletin applies to OMNI 3000 and 6000 liquid and gas
flow computer metering systems beginning with the release of firmware
versions/revisions 20.73+ through 27.73+. It is not applicable to some of
the earlier checksum releases of 20.73 through 27.73 firmware.
Before implementing any of the recommendations in this Technical

Bulletin, thoroughly test the firmware in your particular OMNI flow
computer to determine if its firmware version supports the use of
Variable Statements to synchronize the date/time.

Abstract
available at:
Phone: (281) 240-6161 The most direct method to synchronize time in an OMNI flow computer
Fax: (281) 240-6162
or multiple flow computers is to use a MODBUS ‘broadcast’ WRITE
message. This is the most used method of synchronizing time among
available on our website at: pipeline and process plant SCADA/DCS systems. Note: See sidebar on
www.omniflow.com or send page 3 relating to Ethernet broadcasts.
email to:
techsupport@omniflow.com When there are significant and/or unpredictable transmission delays from
the host system, then it may be desirable to synchronize time via a digital
TB-060801 1
I/O point instead of a Modbus broadcast write via the serial or Ethernet
port link.
Time synchronization of the OMNI 3000/6000 flow computer is

recommended only once or twice per 24-hour period.
OMNI provides a “few” special cases for trapping certain changes made
by Variable statements. The Time and Date 16-bit registers are one of
these special cases. Variable statements within the flow computer are
used to make changes to the clock registers based on a change in state of
a digital input channel.
There are special considerations, detailed below, that must be taken into
account when attempting to synchronize the time via a digital input
channel and Variable statements.
2 TB-060801
TB-060801 Understanding OMNI Flow Computer Time Synchronization
Using a Broadcast Ethernet-to-Serial Port Terminal Servers

Message via Ethernet
Please note that it is not
normally possible to
The use of multi-channel Terminal Servers, which act as a single
broadcast the time and date connection to multiple serial channel converters, can inhibit a fast
to multiple IP addresses
(i.e., multiple devices) via
turnaround in Ethernet communications because they must service each
Ethernet from the same of the serial port devices individually in a “round robin” fashion using
Supervisory system unless
special software is written in
only one Ethernet port. This can result in significantly long periods
the Supervisory system to between communications with the same serial device.
allow it to do so.
To alleviate this problem in an Ethernet communications network, the

However, the broadcast
message is passed through OMNI flow computer can use the SE (Serial-Ethernet) module which
the RS-485 two-wire includes a multiplexer function that supports point-to-point Ethernet
repeater serial port of the
SE module to other OMNI’s connections and/or an Ethernet-to-Serial connection by utilizing its
or other Modbus devices repeater port much like a Terminal Server. However, unlike a Terminal
connected to the flow
computer’s SE module
Server, the multiplexing function provides for up to four independent and
repeater port. simultaneous Ethernet connections (i.e., multiple pipes) on the same
Ethernet port which can significantly increase data throughput with the
This means that the flow
computer with the SE multiple RS-485 2-wire serial devices that can be connected to the SE
module installed in it module repeater port.
requires the time/date be
sent using its specific
Modbus ID address but all This multiplexer function permits the Supervisory system to have
other devices connected to separate programs, if desired, utilizing independent simultaneous
its repeater port can be
synchronized with a Ethernet connections to the flow computer(s), for the purpose of
broadcast message. synchronizing dates and times or for exchanging other data. In addition,
(See OMNI Technical the four independent connections can be using different communication
Bulletin TB020101C for protocols if desired. Supported protocols are TCP/IP (i.e., encapsulated
details on the use of the
Serial-Ethernet module).
Modbus) and Modbus/TCP.
Background
Some registers contain values that are checked at certain parts of the
program execution (like an alarm limit, for example), and can be changed
at will at any time. Others, such as the Time and Date, or serial port baud
rate settings, require an exception routine to run any time they are
changed. The exception routine might be needed to set up program
Getting Tech Support pointers, check the validity of the setting, or manage interrupts while a
OMNI Technical support is hardware chip (e.g., the Real-Time Clock) is written to. When registers
available at: are written to via Modbus, an OMNI flow computer automatically checks
Phone: (281) 240-6161 for and runs any exception routines as needed.
Fax: (281) 240-6162
Register changes made via OMNI Variable statements act like the old
available on our website at: 'Peek' and 'Poke' statements in BASIC. Because they are created by the
www.omniflow.com or send user, it is impossible to anticipate what the user is likely to do and
email to:
techsupport@omniflow.com duplicate the exception processing of the serial I/O routines.
TB-060801 3
It is possible to modify the Time and Date via the registers and also have
the exception routine execute to WRITE to the hardware registers of the
RTC (Real Time Clock) chip.
Caution: OMNI advises against doing multiple WRITES to the RTC's

hardware registers as this could cause shortened, missing, or extended
calculation cycles. For this very reason, OMNI also advises against
using the peer-to-peer feature of the OMNI flow computer in an attempt
to keep time synchronized between multiple flow computers.
The Time (Hours, Minutes, Seconds) and Date (Month, Day, Year) can
be modified by writing to the registers located at Modbus addresses 3867
through 3869 and 3870 through 3872 respectively. These are the only
Time and Date registers that can do this via Variable statements. (e.g.,
one cannot modify Time and Date using the Time and Date ASCII
registers or Long Integer registers, only the 16-bit registers).
Note: When writing the Time or Date in the OMNI via Modbus link, you
may write to either the ASCII registers or the 16-bit registers.
To minimize the number of Variable statements required, you may want

to consider synchronizing only the minutes and seconds, or possibly only
the seconds.
Example
OMNI has provided the digital I/O hardwired signal to synchronize the
hardware clock registers as an “alternative” method. The negative of this
approach is that the user must send the digital pulse at a certain time of
day. To avoid the possibility of jumping the OMNI past a time trigger
event, such as an hourly report time, a user should execute the
synchronization at some unusual time, like 03:17:30 AM for example
(i.e., distinctly apart from an hour, half or quarter hour time line, at which
times critical totalization and averaging functions are occurring inside the
flow computer).
Note: Synchronizing the time in the flow computer at non-critical hours

applies for any method of time synchronization - whether writing the time
via Modbus (including Ethernet) or using the digital input with variable
statements.
In the example that follows, given in Figure 1, it is assumed that digital

I/O point 5 will be used to synchronize the clock at 03:17:30 AM.
4 TB-060801
Getting Tech Support Digital I/O Assignment

available at: Figure 1 below illustrates the use of the OmniCom for Windows PC-
Phone: (281) 240-6161 based program to configure a Digital I/O as an input to accept the signal
Fax: (281) 240-6162 that will trigger the time synchronization.
email to:
Figure 1: Digital I/O Configured as Input.
TB-060801 5
Boolean Statements
Figure 2 below illustrates the Boolean Statements used to 1) transfer the
status of the digital input to a 2-second momentary scratchpad register to
ensure detection, and 2) detect a transition of Lo to Hi of the digital input.
Figure 2: Boolean Statements
1025: 1650=1650+1005 (Ensures that digital I/O 5 is greater than 500

mS by passing its status to a 2-second
momentary register at address 1650)
1026: 7025*7026&7026 (Detect rising edge of 7026 [actually Digital

I/O 5 low to high transition])
6 TB-060801
Getting Tech Support Variable Statements

available at: Figure 3 below illustrates the Variable Statements used to 1) save the status
Phone: (281) 240-6161 of the digital input for comparison against the next cycle for purposes of
Fax: (281) 240-6162 determining if a change has occurred in the digital input status, 2) determine
Technical information is if the change in the digital input signal was specifically a Low to High
available on our website at: transition, and 3) setting the Hours, Minutes, and Seconds when
email to:
synchronizing the time.
Figure 3: Variable Statements
7025: 7026 (state of 1650 previous 500 mS cycle)
7026: 1650-#1 (7026= -1 means 1650 false, 7026= +0 means 1650

true. When a Boolean statement calls the status of
a Variable statement, a value of 0 or greater in the
variable statement is considered true and only a
negative value is considered false)
7027: 1026)3867=#3 (if Boolean statement 1026 is true, Set Hours to 3)
7028: 1026)3868=#17 (if Boolean statement 1026 true, Set Minutes to 17)
7029: 1026)3869=#30 (if Boolean statement 1026 true, Set Seconds to 30)
TB-060801 7

Although the flow computer updates the Time registers in three
separate Variable statements, the actual values are written to the
available at: hardware chip all at once at the end of the Variable statements
Phone: (281) 240-6161
execution.
Fax: (281) 240-6162
available on our website at: Programmable Statements Analysis
email to:
techsupport@omniflow.com Digital I/O point 5 must be activated for at least 101 mS to ensure
that it is captured by the flow computer. The amount of time it
remains active after that is not important. Boolean statement
1025 is used to “OR” the digital I/O state into a 2 second “one-
shot” Boolean scratchpad register (1650) for the purpose of
stretching the digital input signal to greater than 500 mS. This
step can be eliminated if the digital input signal fed into the
OMNI digital I/O point 5 can be guaranteed to remain active high
for more than 500 mS.
The OMNI then ensures that the “one-shot” action is

synchronized to the 500 mS calculation cycle by monitoring its
value for this calculation cycle and the previous cycle using
variable statements 7025 and 7026. A 500 mS flag (Boolean
statement 1026) is then created which goes TRUE for 1
calculation cycle (500 mS) on the rising edge (i.e., Low to High
transition) of digital I/O 5 (status passed to registers 1650 and
1026). This 500 mS flag is used by statements 7027, 7028, and
7029 to move constants representing 03, 17, and 30 into the Time
registers at addresses 3867, 3868, and 3869 respectively.
A user can, if preferred, transmit predetermined values for Hours,

Minutes, and Seconds, into three 16-bit Modbus “Scratch Pad”
registers located at register range 3501 through 3599 and move
these values into 3867 through 3869 when digital input 5 (or
Boolean scratchpad 1650) goes high. The above example does
not do this, it uses predefined constants instead.
8 TB-060801

Volume 5d

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Volume 5d

Uploaded by

Copyright:

Available Formats

Volume 5 Compendium of Technical Bulletins

COMPENDIUM OF TECHNICAL BULLETINS

All Revs  05/07 i

Technical Bulletins in Volume 5 (Continued)

060419 OMNI 3000/6000 Totalizer Functions

ii All Revs  05/07

Last Updated: 05 05 2003 TB # 960701

Overview of OmniCom Configuration PC

TB-960701  ALL REVS 1

Configuring the Flow Computer

2 TB-960701  ALL REVS

Operations Utilities and Help

Omni Flow Computers encourages the installation of a telephone dial-up

Passwords Using OmniCom

TB-960701  ALL REVS 3

Local Keypad Access

Changing Passwords at the Keypad

4 TB-960701  ALL REVS

Setting Up the Initial 'Level B' and 'Level C' Passwords

Maintaining the Modbus Port Password Using OmniCom

TB-960701  ALL REVS 5

Disabling Modbus Port Passwords

6 TB-960701  ALL REVS

For Further Help - If you

TB-960701  ALL REVS 7

I/O Point Assignment List

8 TB-960701  ALL REVS

US VERSIONS METRIC VERSIONS

Orifice / Differential Pressure Liquid Orifice / Differential Pressure Liquid

Archive Start/Stop Command

For Further Help - If you

TB-960701  ALL REVS 9

Omni Front Panel Emulator

10 TB-960701  ALL REVS

Registration of License and Software Support

TB-960701  ALL REVS 11

12 TB-960701  ALL REVS

Communicating with Allen-Bradley

TB-960702  ALL REVS 1

Protocol and Error Checking

4th and 5th Digit from the Right Identifies Type of

2 TB-960702  ALL REVS

3rd Digit from Right Identifies which Area within the

How the Allen-Bradley Accesses the Omni

TB-960702  ALL REVS 3

MODBUS INDICES VERSUS PLC-5 ADDRESSES

Valid Starting Addresses of PLC-5 Files

32-Bit IEEE Floating Points

32-Bit IEEE Floating Points

4 TB-960702  ALL REVS

Date: 05 09 03 Author(s): K. E. TB # 960703

Storing Archive Data within the Flow

TB-960703  ALL REVS 1

2 TB-960703  ALL REVS

TB-960703  ALL REVS 3

Raw Data Archive Point Addresses

Archive #1 Record Access Address Read Only 0701

4 TB-960703  ALL REVS

Archive #10 Record Access Address Read Only 0710

Retrieving Text Archive Data Including Alarm and Audit

Retrieving Text Archive Data Using OmniCom

For use with Omni Revisions 2x.70 and below:

For use with Omni Revisions 2x.71 and above:

All Revs 05/07 i

ii All Revs 05/07

TB-960701 ALL REVS 1

2 TB-960701 ALL REVS

TB-960701 ALL REVS 3

4 TB-960701 ALL REVS

TB-960701 ALL REVS 5

6 TB-960701 ALL REVS

TB-960701 ALL REVS 7

8 TB-960701 ALL REVS

TB-960701 ALL REVS 9

10 TB-960701 ALL REVS

TB-960701 ALL REVS 11

12 TB-960701 ALL REVS

TB-960702 ALL REVS 1

2 TB-960702 ALL REVS

TB-960702 ALL REVS 3

4 TB-960702 ALL REVS

TB-960703 ALL REVS 1

2 TB-960703 ALL REVS

TB-960703 ALL REVS 3

4 TB-960703 ALL REVS

TB-960703 ALL REVS 5

6 TB-960703 ALL REVS

* SETUP MENU *

* MISC SETUP *

TB-960703 ALL REVS 7

* MISC SETUP *

8 TB-960703 ALL REVS

TB-960703 ALL REVS 9

10 TB-960703 ALL REVS

TB-960703 ALL REVS 11

12 TB-960703 ALL REVS

TB-960703 ALL REVS 13

14 TB-960703 ALL REVS

TB-960704 ALL REVS 1

2 TB-960704 ALL REVS

TB-960704 ALL REVS 3

4 TB-960704 ALL REVS

TB-960704 ALL REVS 5

6 TB-960704 ALL REVS

TB-960704 ALL REVS 7

8 TB-960704 ALL REVS