OMNI Flow Computers, Inc.
Last Updated: 09 April 09 TB # 980401B
Peer-to-Peer Basics
Contents
User Manual Reference - Scope ......................................................................................................... 1
This technical bulletin
complements the Abstract ...................................................................................................... 2
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 .74+.
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 a
Redundant Flow Computer
Setting up Transactions ........................................................................... 8
Application What Modbus Function Codes Are Used ............................................... 8
Volume 1 - 1.6.3. Serial
Communication Modules Special Considerations when ‘Modicon Compatible’ is Selected for
Port #2 ........................................................................................................ 8
Peer-to-Peer
Using Peer-to-Peer with Micro Motion Coriolis Mass Meters ............ 9
Communications - The The Micro Motion Meter is a Modicon Compatible Device ................................... 11
peer-to-peer communication
feature allows you to multi-
Setting Up the Peer-to-Peer Transactions ............................................ 11
drop up to 32 flow
computers and other
devices in RS-485 serial
communications mode, and
Figures
up to 12 using RS-232-C Figure 1. OMNI 6000 (3000) Peer-to-Peer Wiring Requirements using the
communications. RS-232-C Termination Option ............................................................. 4
Figure 2. OMNI 6000 (3000) Peer-to-Peer Wiring Requirements with PLC
Peer-to-Peer Redundancy using a Standard RS-232 to RS-485 Converter Module ...................... 5
Schemes - Redundancy
schemes allow for Figure 3. OMNI 6000 (3000) Peer-to-Peer Wiring Requirements using the
uninterrupted measurement RS-485 Two-wire Multi-drop ................................................................ 6
and control functionality by
interconnecting two Figure 4. OMNI 6000 (3000) Peer-to-Peer Wiring Requirements with PLC
identically equipped and
configured flow computers.
using the RS-485 Two-wire Multi-drop ................................................ 7
Figure 5. OMNI 6000 (3000) Peer-to-Peer Wiring Requirements with Micro
Motion RFT Transmitters using a RS-232 to RS-485 Converter ......... 9
Figure 6. OMNI 6000 (3000) Peer-to-Peer Wiring Requirements with
Micro Motion RFT9739 Transmitters using the RS-485 Two-wire Multi-
drop. 10
52-0001-0001 Rev B 1
OMNI 6000 / OMNI 3000 Flow Computers Technical Bulletin
Getting Customer Scope
Support - Customer
support is available at: All firmware revisions Version .70+ of OMNI 6000/OMNI 3000 Flow
(281) 240-6161 Computers have the Peer-to-Peer Communication feature.
Email should be sent via
the WEB Page at: Abstract
[Link]
Communications between OMNI flow computers is accomplished using the
or email to:
helpdesk@[Link]
peer-to-peer function. This function is available only on Serial Port #2 with
data being transmitted and received using Modbus RTU protocol. A data
transaction list within each flow computer defines each Read or Write
operation to be transacted for that computer. A maximum of 16
transactions per flow computer are available. The transaction list must be
contiguous (i.e., an empty transaction will be treated as the end of list).
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 3 ticks (150 msec).
2 52-0001-0001 Rev B
TB-980401B 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 The peer-to-peer function is not limited to multiple OMNI flow computers.
note that in a peer-to-peer Some applications simply require a single flow computer master to
system, only the flow
communicate with a variety of Modbus slave devices which may be flow
computers that have a non-
zero entry for ‘Next Master computers, PLC’s etc. In these cases, the entries 1 and 2 above would be
in Sequence’ are limited to set to 1 in the master flow computer only, signifying only one master is in
using Serial Port #2, all of the system. Entry 3 above would normally be set to 3 but may need to be
the other flow computers increased depending upon the message response time of any foreign
are simply acting as
Modbus slaves and can use Modbus devices in the system.
any valid Modbus serial
port.
52-0001-0001 Rev B
3
OMNI 6000 / OMNI 3000 Flow Computers Technical Bulletin
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 ‘tri-statable’
RS-232-Compatible serial
port, which unlike a normal
RS-232 port, can be multi- Omni #1 Omni #2 Omni #3 Omni #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
Figure 1. OMNI 6000 (3000) Peer-to-Peer Wiring Requirements using
the RS-232-C Termination Option
4 52-0001-0001 Rev B
TB-980401B Peer-to-Peer Basics
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
5 5 Converter
(Disable Echo) PLC
6 6
R
7 7 R TX-A A
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
Figure 2. OMNI 6000 (3000) Peer-to-Peer Wiring Requirements with PLC
using a Standard RS-232 to RS-485 Converter Module
52-0001-0001 Rev B
5
OMNI 6000 / OMNI 3000 Flow Computers Technical Bulletin
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-
Serial I/O Module # 68- wire, multi-drop mode.
6205, the flow computer
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
Figure 3. OMNI 6000 (3000) Peer-to-Peer Wiring Requirements using
the RS-485 Two-wire Multi-drop.
6 52-0001-0001 Rev B
TB-980401B Peer-to-Peer Basics
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.
Getting Customer
Support - Customer
support is available at:
(281) 240-6161
Email should be sent via
the WEB Page at: Omni #1 Omni #2
[Link] TB3 TB3
or email to: (TB2) (TB2)
helpdesk@[Link] 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
Figure 4. OMNI 6000 (3000) Peer-to-Peer Wiring Requirements with PLC
using the RS-485 Two-wire Multi-drop.
52-0001-0001 Rev B
7
OMNI 6000 / OMNI 3000 Flow Computers Technical Bulletin
Setting up Transactions
To process a transaction the flow computer requires the following data for
Modbus Broadcast
each transaction:
Address ‘0’ - This address
only applies to write Slave ID : The Modbus address of the target
transactions.
device. This can be any valid Modbus
address 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 determines 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 03 H for reads and 10 H for writes. Boolean
variables are packed 8 to a byte starting at LS bit and use function codes
01 H for reads and 0F H 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 52-0001-0001 Rev B
TB-980401B Peer-to-Peer Basics
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 to make the interface
to the Micro Motion meter more useful and 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
7 7 R TX-A 27 (Z22)
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.
Figure 5. OMNI 6000 (3000) Peer-to-Peer Wiring Requirements with
Micro Motion RFT Transmitters using a RS-232 to RS-485
Converter.
52-0001-0001 Rev B
9
OMNI 6000 / OMNI 3000 Flow Computers Technical Bulletin
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 Omni #1 Omni #2 Note: Termination resistors
industry standard applied to TB3 TB3
OMNI flow computers; i.e., may be required with some
(TB2) (TB2) installations.
the flow computer’s A
channel connects to Micro 1 1
Motion’s B channel. OMNI
has tested this connectivity
2 2
with the Micro Motion 3 3 Micro Micro
RFT9739 Field-Mount Motion Motion
Transmitter, but connecting 4 4 RFT9739 RFT9739
to the rack-mount version 5 5 #1 #2
has not yet been tested.
Information on this 6 6
(B) (B) (B) (B)
connectivity has been 7 7 26 (D22) 26 (D22)
provided by Micro Motion,
Inc. Please contact Micro 8 8
Motion for further 9 9 120Ω
information.
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.
Figure 6. OMNI 6000 (3000) Peer-to-Peer Wiring Requirements with
Micro Motion RFT9739 Transmitters using the RS-485 Two-
wire Multi-drop.
10 52-0001-0001 Rev B
TB-980401B Peer-to-Peer Basics
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
I/O point must be assigned fluid from the Micro Motion device (Modbus ID #2) and stores it in data
to ‘99’ and Serial Port #2
base point 7108 (unfactored density, meter run #1).
must be assigned to be
‘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
address before using it in a which contains packed alarm status bits. These are stored in a special
transaction.
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.
52-0001-0001 Rev B
11
